How to set up JIRA for multiple similar projects

[Phil Wardell]

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.

Thanks

[Gabrielle Bautista [ACP-JA]]

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.

[Phil Wardell]

Thanks for your advice. Would you recommend that we create a different project for each website?

[Gabrielle Bautista [ACP-JA]]

Yes, that is usually the best way to go IMHO. That way, you can fully utilize Components, Versions etc... for each Project without any dependency with the other project.

[Phil Wardell]

Could a board for each website work as well, or do you foresee problems with that approach?

[Gabrielle Bautista [ACP-JA]]

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.