Linking a story w/ subtasks across 2 boards

[Krupa Savjani]

I have cloned the story with its subtasks on Board 1 (Next Gen) successfully, and I have assigned it to the relevant sprint for the subsequent Board 2 (Scrum), however, the story is not showing on Board 2.

Use case:
I work a cross two teams, and therefore 2 boards. The stories that I work on must be visible on each. Rather than duplicate the number of stories/subtasks

1) I'd like my stories and sub-tasks to be linked across the two boards
2) I'd like its progress to be synced

Is this possible?

I am not a seasoned JIRA user so answers in layman's terms are appreciated :)

[Trudy Claspill]

Hello @Krupa Savjani 

Welcome to the community.

You said "Board 1 (Next Gen)" and "Board 2 (Scrum)". Are these boards looking at issues in the same project? Do all the issue IDs have the same project key, like ABC-1, ABC-2, ABC-3, where "ABC" is the project key? Or are they different projects?

If these boards are looking at different projects, is the "Board 2 (Scrum)" board also viewing data from a Next Gen project?

Why does your work for Team A need to be visible in Team B's board? Are the stories actually relevant to both teams, or do you want them visible in both teams' boards because you work in both teams and you want or need each team to see all your work?

Answers to these questions will help us provide you with better guidance.

[Krupa Savjani]

Hey @Trudy Claspill 

Thanks very much! The latter.

I want them visible in both teams' boards because I work in both teams and I need each team to see my work

Board 1 houses most of my projects, Board 2 should house some of my projects (as there is overlap in projects across two Boards, however each board, is owned by a separate product owner)

[Trudy Claspill]

Hello @Krupa Savjani 

There is not a built in feature in JIRA Cloud specifically for synchronizing cloned issues, but you might be able to accomplish it using Automation for JIRA functionality. You would have to work with the project admins to get that set up. Or there might be apps you could buy that might help you synchronize statuses between linked issues. The difficult part would be setting up something custom that would work for only your cloned issues vs. all cloned issues.

But I also need to know the answer to the question - what type of project is being viewed with Board 2?

Additional advice I might give you depends on whether Board 2 is being used to view a Next Gen project or a Classic project.

[Bill Sheboy]

Hi @Krupa Savjani  -- Welcome to the Atlassian Community!

Agreeing with what @Trudy Claspill suggests, please consider the problem you are trying to solve: improve visibility with you assigned to two teams at once leading to reduced capacity.

You note that one of the teams is using Scrum, and so cloning/showing issues from your other team on the scrum board's filter could impact their reporting.  Same for the other team, but you do not indicate if they are using Scrum or Kanban.

Please consider chatting with the teams to learn how to make your capacity visible while not impacting team priorities, reporting, etc.  Thanks!

Best regards,

Bill

[Ash Pitt]

Hey @Krupa Savjani 

Generally I'd be looking at using classic projects if you're after that type of view process. Next-Gen projects are typically stand-alone.

However, a potential solution you could try.

In a classic project, create a kanban board that can include issues from both of your projects for your visibility, or utilising dashboards.

I'd also recommend checking out the following articles for some further insight!

• https://community.atlassian.com/t5/Next-gen-articles/Everything-you-want-to-know-about-next-gen-projects-in-Jira/ba-p/894773 AND 
• https://support.atlassian.com/jira-service-management-cloud/docs/learn-the-differences-between-classic-and-next-gen-projects/