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; } } }

Multiple projects sharing one story - where do the points go when its moved to done?

Alisha Maistry

Good day.

I have two projects sharing one story. The story is logged onto board A and once it reaches a certain column it then goes onto board B using a filter query, Im not sure why but when the story is done and closed on board B it then reopens and leaves board B.

Green Mambas - Agile Board - JIRA.png

I would like the ticket to stay in done on board B and the point to contribute to the burn down of board B.

Please help.

Accepted answers

Nic Brough -Adaptavist-

Actually, you don't have a story in two projects, they can only belong to a single project.

You do have it on two boards though. A board is a view of a selected set of issues, and you've got the selections matching the issue, so it appears on both boards. Remember that it is a single issue you are looking at, not separate ones, so anything you do to it on one board will be changed on the other.

So, you'll need to look at how the issue status is mapped in both boards. If you want an issue to be done on one board and not another, you'll need to have different status maps.

A simple example, imagine a workflow of to-do -> in-dev -> in-test -> done

If you have two boards, one for dev and one for test, you can achieve what you want by havving the columns set p as:

Dev board: To-do = To-do, in-progress = in-dev, Done = in-test and done

Test board: to-do = to-do and in-dev, in-progress = in-test, done = done

All comments

Nic Brough -Adaptavist-

Actually, you don't have a story in two projects, they can only belong to a single project.

So, you'll need to look at how the issue status is mapped in both boards. If you want an issue to be done on one board and not another, you'll need to have different status maps.

A simple example, imagine a workflow of to-do -> in-dev -> in-test -> done

If you have two boards, one for dev and one for test, you can achieve what you want by havving the columns set p as:

Dev board: To-do = To-do, in-progress = in-dev, Done = in-test and done

Test board: to-do = to-do and in-dev, in-progress = in-test, done = done

Alisha Maistry

Hi Nic,

Thank you for your response, everything you have said above makes sense.

To give you some background, Project A is our support team who then logs issues on their board, board A. As the item gets investigated and confirmed as being a bug it will then show on the relevant dev teams board (in this example project B and board , the dev team then fixes the bug and closes the ticket - since the work is done by Project B, I need it to reflect in their stats and on their burn down chart. Am I doing this in the most efficient way?

Also if the issue is a feature request it does not pull into project B's backlog, however it does if I change it to a story. Can you explain why? My filter doesn't make any specific mention to what type of issue it should bring.

Nic Brough -Adaptavist-

The way Atlassian expect you to do this is for Project A to manage their issue as the front end of a request from a person, and when Project B need to do some work on it, create a linked issue in B for B to put through their process, and using the link to update A when it's ready for them to talk to the user or publish something etc.

That's a process built into Jira Service Desk though, rather than Jira Software.

Drawing it into a board for project B to use is another way to handle it, and not a bad one at all, although Jira isn't really built to support it.

You'll need to take a close look at your board filters and columns to see how the backlogs are being defined.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

atl-gruland