3 ms·
I would recommend Jira - get the GreenHopper plugin to make it less "old-fashioned", but it's the right tool for the job. You can customize it if you want to go
by web007 11y ago
I would recommend Jira - get the GreenHopper plugin to make it less "old-fashioned", but it's the right tool for the job. You can customize it if you want to go down that rabbit hole, but the built-in workflows should get you started. Projects, epics and tags should solve the problem of finding issues. Set each client as a project, or more likely as an epic so you can have one view for your developers / designers that splits by client.
Currently using Pivotal Tracker after coming from a Jira shop, and it's awful. Others seem to like it, but it's too simplistic for my taste. Even something as simple as "A blocks B" isn't possible, and seems to be by design.
- ashwinaj 11y ago+1 for Jira. It's clean, simple and easy to understand.
- bmulholland 11y agoPivotal Tracker is great for what it's intended for, but it's a very opinionated tool. It's not a good repository for storing a large number of bugs or features, and as such doesn't have fancy features like "X blocks Y". If you have an external system for your features (we just use a google docs roadmap) and immediately triage bugs (will fix next sprint, or won't fix), it works great. Lots of discipline required, though, and it takes some understanding of their specific approach before things start to make sense.
- tajen 11y agoSince October, JIRA+GreenHopper = JIRA Software.
- maxxxxx 11y agoJira with Bitbucket Server works for us pretty well. You just have to resist the urge to customize too much and stick to the basics instead. BTW you don't need Greenhopper anymore. Jira Agile is now integrated into Jira software