I am involved in the process of converting an existing project to use agile, and am wanting to use Greenhopper for planning. The project already uses JIRA for tracking features, enhancements and bugs.
I am trying to resolve the different uses of VERSION in greenhopper to the traditional use in JIRA. For example for the current release we have three branches targetting three different releases:
We use the VERSION in JIRA to track what releases we have, and which releases a feature/bug is in or planned for.
Now we want to start organising our planning into sprints/timeboxes, and Greenhopper uses the VERSION to track each sprint. It is possible that in any sprint the team could end up doing work for all three releases.
In my last project we faced the same issue and ended up resolving it by having separating traditional JIRA tickets from Greenhopper stories in seperate projects. But this meant that every Greenhopper story had to be linked back to the original JIRA ticket that it was related to. This also required that the developers maintain the workflow and comments on two linked issues, and then me manually going through them all at the end of a sprint to audit and synchronise everything. This was a major pain point that we never resolved.
On this project I am investigating using a single project and using the features/bugs directly and not using epics/stories. I see two options here.
Am I missing something obvious here, or is there a recommended best practice for resolving this issue?
Thanks Shaun, that looks like it would do the job. Shame that my company is on an older version of Greenhopper that pre-dates the RapidBoard. But I am sure that will get upgraded in due coarse, and then I can start playing with it.
In the meantime our tactical hack is to use the JIRA version for the sprint planning and then create our production release numbers as tasks with links to the issues that are included in the release. I think that this will work ok for us, but it looks that when we get the Rapid Board this will make thinks a lot easier for us.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs