nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Urgent - Automate copy of User Stories from Master Backlog to Project Backlog for selected Services

Muddu

Experts – we are looking to implement automation in Jira and would like to understand if it is possible and how to go about it. We have multiple services that we offer to a client and a client can select one or more of these services as their solution. There is also a master backlog of user stories each tagged to a service. Now depending upon the selected service(s), a subset of the user stories that correspond to the select service(s) should be picked up / cloned and added to a backlog of new project. We would also like the ability to generate metrics on this new project, develop dashboards, compute total story points, etc

We have a pressing urgency to identify a solution for the above. Any help in this regard is highly appreciated.

Accepted answers

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

I would not recommend doing this at all. Duplicating data is not efficient and it doesn't help the end users because you end up having to duplicate change back into the original issue (which people will almost always forget to do)

The backlogs are part of a board, and a board is a view of a selection of issues, it is not a container.

The easiest and best way to work in your situation is probably going to be to amend the boards for each team so that they draw in the issues the team needs to address.

If, for example, you have build services called "Lego", "Duplo" and "Meccano", then add these as options to a "services" field (a multi-select will work well for this). When people create an issue, they set one or more of the services on the issue.

Then create a board for each of the three teams. The board filters should be "services = Lego", "services = Duplo" and "services = Meccano".

With this, there's no need to duplicate issues (which will let them drift apart).

Rilwan Ahmed

Hi @Muddu ,

1a. Issue types (i.e. Lego, Duplo, Meccano, Domes, Whistle) doesn't come as checkbox. They are dropdown options. If you need same Project ABC issue types for project XYZ, then while creating new project, create project with shared config. (Refer section "Create a project that shares its configuration with another project" in https://support.atlassian.com/jira-software-cloud/docs/create-a-new-project/)

If you want only few issue types for new project, then create a new issue type scheme, add only requested issue types to it and then map to the new project. Also update workflows scheme accordingly.

1b. Refer https://support.atlassian.com/jira-software-cloud/docs/create-and-plan-work-with-scrum-and-kanban/ for creating backlogs

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

The backlogs are part of a board, and a board is a view of a selection of issues, it is not a container.

The easiest and best way to work in your situation is probably going to be to amend the boards for each team so that they draw in the issues the team needs to address.

Then create a board for each of the three teams. The board filters should be "services = Lego", "services = Duplo" and "services = Meccano".

With this, there's no need to duplicate issues (which will let them drift apart).

Muddu

Hello @Nic Brough -Adaptavist- !

Thank you for your response. Let me structure my question in a better way with example.

MNC Solutions, my client (not their real name), has a vast repository of reusable issue types that serve as a master template for their Master backlog. These issue types are categorized according to the services they offer and are labeled accordingly.

Those Issue types are parked under my client Jira Project say 'MASTER PROJECT'

For example, some of the services provided by my client are Lego, Duplo, Meccano, Domes, Whistle

The reusable issue types have been grouped together based on the type of service they provide.

For instance, In the Master Backlog Repository there are 5 Services as below:

Lego service type has 100 User Stories/Tasks,
Duplo service type has 80 User Stories/Tasks,
Meccano service type has 60 User Stories/Tasks,
Domes service type has 40 User Stories/Tasks, and
Whistle service type has 20 User Stories/Tasks

My client, MNC Solutions operates multiple Jira projects simultaneously, with each project dedicated to serving a specific client, i.e. the client of my client.

MNC Solutions' clients have the flexibility to choose one or more services from the range of services offered by MNC Solutions.

For instance,

Client ABC Corp may opt for any three services, such as Lego, Duplo and Meccano offered by MNC Solutions Similarly,
Client PQR Corp may choose any two services, such as Meccano & Domes offered by MNC Solutions
Client XYZ Corp may select any four services, Lego, Duplo, Meccano & Whistle offered by MNC Solutions

My client, MNC Solutions, has outlined specific requirements that need to be fulfilled when a new client, such as XYZ Corp, creates a Jira project on MNC Solutions' platform.

1a. When a new Jira project ("XYZ Corp - MNC Solutions") is created in MNC Solutions' Jira platform, the client should be able to choose any of the services (Lego, Duplo, Meccano, Domes, Whistle) by selecting checkboxes available in the Jira project screen.

1b. Once the client, XYZ Corp, confirms the required services, a backlog should be created in MNC Solutions' Jira platform under the project named "XYZ Corp - MNC Solutions".

The backlog should contain all the issue types related to the services selected by XYZ Corp i.e. (Lego, Duplo, Meccano & Whistle).

To achieve this, we believe the issue types should be cloned from the reusable issue types available in MASTER PROJECT of MNC Solutions.

This would result in 260 issue types or issue types created in the backlog of the project "XYZ Corp - MNC Solutions Jira" as the total number of issue types for the selected services is

260 (100 issue types for Lego, 80 issue types for Duplo, 60 issue types for Meccano, and 20 issue types for Whistle).

Please let me know how to build a solution for my Client's requirement 1a and 1b.

Requesting @Rilwan Ahmed and @Alex Koxaras -Relational- to share your thoughts in this as well.

unknown

@Rilwan Ahmed @Alex Koxaras -Relational- please share your inputs on above query.

Alex Koxaras -Relational-

@[deleted]and @Muddu are you the same person? It's quite odd that @Muddu posted the opposite thing in this thread https://community.atlassian.com/t5/Jira-Software-questions/What-all-Feature-we-can-automate-in-Jira/qaq-p/2276554#U2279365

Rilwan Ahmed

Hi @Muddu ,

If you want only few issue types for new project, then create a new issue type scheme, add only requested issue types to it and then map to the new project. Also update workflows scheme accordingly.

1b. Refer https://support.atlassian.com/jira-software-cloud/docs/create-and-plan-work-with-scrum-and-kanban/ for creating backlogs

Muddu

Thank you @Rilwan Ahmed for your input. I will take a look into the approach that you have suggested and read through the link that you shared.

Once again Thank You Rilwan for helping us with your valuable time and knowledge.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud