I am able to see the same issue in two different scrum boards but unable to make changes to the ticket. When I move the ticket up the workflow in one board it disappears from the other board.
I tried automation rules, but couldn't figure it out.
How do I get an issue to be edited in two different boards?
Can someone please help me with a step-by-step process of editing an issue in two different boards.
Each column in a board can be mapped to one or more statuses. You can also have swimlanes based on things such as JQL, Assignees, Projects etc.
If a ticket is disappearing on one board but not another, then it is either at a status not mapped to a column or doesn't satisfy the filter on the swimlanes on the board. Check the board configuration for both boards to identify why it is showing on one board but not the other (... > Board Settings).
Hey Alex,
I guess what I'm trying to ask is can two issues have the different statuses in two at the same time?
For example, after the Design stage, the issue is worked on by Development and QA at the same time. Each team has their own pathway for the issue. Can the issue move along two different pathways at the same time?
If yes, could you please tell me how I can configure it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jacob,
When we talk about a "pathway" on a board, we are actually talking about the steps in the issue workflow. A board is just a way of displaying an aggregated view of multiple issues grouped by status(es).
If you want two different teams to work on an issue and have a different status for each team, you'll need to adopt a sub-task approach. i.e. for each issue that needs to be worked on by the QA team, have a QA subtask under that issue. This can then have its own workflow entirely. This is how we work (in fact we have multiple subtasks for each issue).
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.