Skip to content
This repository has been archived by the owner on Sep 29, 2022. It is now read-only.

Post: Github Projects vs Pivotal Tracker #23

Open
mirisuzanne opened this issue Sep 14, 2016 · 6 comments
Open

Post: Github Projects vs Pivotal Tracker #23

mirisuzanne opened this issue Sep 14, 2016 · 6 comments

Comments

@mirisuzanne
Copy link
Member

We've been on PT for years. Now we're playing with a new toy. What have we found so far?

@mirisuzanne mirisuzanne changed the title Post about Github Projects vs Pivotal Tracker Post: Github Projects vs Pivotal Tracker Sep 14, 2016
@agriffis
Copy link

If you're taking requests... :-)

One of PT's defining features seems to be velocity tracking and prediction. Is that something you used in PT? Do you miss it in GP?

@stacyk
Copy link
Member

stacyk commented Sep 23, 2016

I love the idea of github projects. I'd love to try it out a bit more but am on board whichever direction we go. After @jgerigmeyer's PT demo I think there are many features that I personally haven't been using/paying attention to that are interesting. On the other hand, I have no idea what Github Projects is capable of (yet).

@agriffis I haven't personally noticed Velocity Tracking and prediction, but like I mentioned above there are features in PT that are interesting that I need to start using. As a team, I do believe some Birds do use these features.

@agriffis
Copy link

@stacyk Interesting, thanks. Maybe when this becomes a blog article you can elaborate on those many interesting features of PT. :-)

@mirisuzanne
Copy link
Member Author

@agriffis I think we just started taking requests. :)

@hahla
Copy link

hahla commented Aug 9, 2017

Please excuse the complete random question! I was researching the same thing for my team, and was interested if you had any thoughts on this topic roughly a year after opening the conversation? I looked at your project boards on github but didn't see much activity, and before I made an interpretation of that, I wanted to simply ask your thoughts. Cheers

@mirisuzanne
Copy link
Member Author

Hi @hahla – good question! We should really write a follow-up post.

Short story: your observation is right. We found the back-and-forth between "issues" and "projects" somewhat confusing and bulky to manage. I see a lot of promise for this – but it doesn't feel fully featured. I'm still using it for some open-source projects, though I think milestones are even simpler for that use-case – using tags for the status of each issue.

(Our test may be skewed by the fact that most of our projects are still in PT, and it's hard to manage two different task-trackers)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants