How can I select a user story from a different project when using Rapid Boards for Agile

How can I select a user story from a different project when using Rapid Boards for Agile? I want to have a project or projects representing products - with large backogs which will span multiple sepate release projects. I want to be able to create a separate project per quarterly release and select backlog items from one of my master 'product' projects

1 answer

David:

On one of my teams they typically span multiple JIRA projects. Even though there is multiple projects we plan and run through they are one sprint. If you are using Greenhopper v5.9.0 or v5.9.1, what I would do is turn on Scrum in Greenhopper Labs (http://confluence.atlassian.com/display/GH/GreenHopper+Labs). Once you do that create a JQL query (http://confluence.atlassian.com/display/JIRA/Advanced+Searching) that contains all the possible stories (issues) you have. I find that depending on the complexity of your situation there may be some art in writting up a JQL query that covers it.

Once you have your JQL written create a rapid board that uses your JQL query rather then a JIRA project. There are a lot more advanced options like swimlanes and quick filters which can help to keep things straight when working with multiple projects or a lot of stories (issues).

After everything is setup you can use the "Work" tab to take your backlog and add it to a sprint. Currently there is only one sprint avalible, but the Greenhopper team is looking to improve that (http://confluence.atlassian.com/display/GH/The+Future+of+GreenHopper).

Now, the last part that might not be so easy. Once you idenify everything that will be in the sprint, you are going to have to select all of those issues and move/copy them to your new "quarterly project." I would do that by bulk updating all the issues in a given sprint in Issue Navigator (http://confluence.atlassian.com/display/JIRA/Modifying+Multiple+%28%27Bulk%27%29+Issues). This will not be a super smooth operation as some of the original values of fixVersion or components may not match for example. The cool thing is JIRA will keep the old ID so that if someone types it in they will automatically be redirected to the moved issue.

From what I am reading in your description I think the above should work. You will need to maintain your JQL a bit more (because your not using fixVersion for releases) and bulk edit issues, but beyond it should be fairly normal. Hopefully this helps.

Respectfully,

-Jeremy Neuharth

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Mar 28, 2018 in Jira Software

Can a company’s culture make or break agile adoption?

Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...

17,622 views 18 20
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you