We are setting up JIRA to help manage the implementation of a front redesign of ten websites. These websites are all quite similar and the same tasks will need to be done on each one.
We have one team making the changes across all the sites and they will start with a week long Sprint 1 on Site A, and the next week will perform the same/similar Sprint 1 on Site B and so on. When Sprint 1 is complete on all sites we will move to Sprint 2 which will consist of items from the backlog common to all sites.
I'm expecting a situation where Sprint 1 is defined and completed, and we then want to duplicate these tasks across all brands. Then the same for Sprint 2.
Please can you advise on the most efficient way to set up JIRA to manage this process, or point me in the direction of something online to help.
Any help will be much appreciated.
What you can do is put a 'label' on a set of tickets that needed to be replicated on for each sprint then use Bulk Clone (https://marketplace.atlassian.com/plugins/com.lbcg.jira.plugins.bulkclone.BulkClone) them for re-use.
We have gone that way before too and it can work. What we did is we created a Scrum of Scrums (http://guide.agilealliance.org/guide/scrumofscrums.html) board to manage multiple agile projects at once.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
@Rachel Wright (Jira Genie), @Billy Poggi (AUG NOVA, DC), and @Dana Jansen (Confluence Queen) are just some of the folks that lead one of the world's most active Atlassian User Group (AUG)....
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