I have an existing board that someone else is managing but I want my board to get a continuous feed

[Jasdeep Joga]

Hi,

I have a Kanban board that is managed by someone else, and I need to have my own Kanban board, which would need a continuous feed from the other board when an issue transitions to a Submitted column. 

How can I establish a board that can gather not only existing data in the parent board but continuously provide a feed whenever an issue transitions to the submitted column?  

[Mykenna Cepek · Accepted solution]

In Jira, Boards are just a view of the issues in a Project.

So simply make another Board based on that Project. You can arrange the columns on this new board however you want. As long as you don't move issues on the board, it can show you a synchronized view separate from the other board.

[Jasdeep Joga]

On my board the the issues will need to go through a dev and test cycle which means the issues will go through the transition.

[Jasdeep Joga]

I was able to make another board but I noticed that the same workflow is being used by both boards and when I made updates to workflow on my board that changed the transition selection options for the other as well.

Is it possible to have 2 boards with their down workflows as well? If yes How?

[Mykenna Cepek]

It's certainly possible to have two separate boards handling different parts of a workflow for a single Jira project. For example:

• Board A1 of Jira Project A is used by the Product Owner and BAs to triage, evaluate, scope, and prioritize incoming work. Their board has columns like "New", "Evaluating", "Approved" and "Canceled".
• Board A2 of the same project is used by Developers and Testers to complete approved work. Their board starts with an "Approved" column, and then uses "In Development", "Testing", "Done", and "Cancelled".

Board A2 is configured to NOT show items in the "New" and "Evaluating" status by mapping those two status values to the "Unmapped statuses" section of the Board Configuration. Likewise Board A1 does not map the four other statuses used by Board A2.

Project A has a single workflow with all the statuses. But each board only shows the appropriate subset of issues based on the issue status. Issues can be transitioned within the scope of each board by dragging the cards to different columns. Note that changing the "Status" field by hand should be discouraged, but is a way to move cards "between boards".

The careful reader will have noticed that I wrote "Canceled" and "Cancelled", which was intentional to identify two similar Status values but they are literally different in Jira. The advantage here is that items "Canceled" on Board A1 do not show in the "Cancelled" column of Board A2. To employ this optimization, be sure to map "Cancelled" on Board A1 to the "Unmapped statuses" column. Likewise, "Canceled" should be unmapped on Board A2.

[Trudy Claspill]

Adding a clarifying point. Note that I'm not disagreeing with what @Mykenna Cepek has stated. I am only saying it in a slight different way.

An issue has one and only one Workflow, which is applied to it based on its issue type and the configuration of its project. The Workflow determines the Statuses to which an issue can be set and how it can be changed from one Status to another Status.

Within a board you can choose to display issues based on any one or more of the  Statuses to which the issue(s) can be set, based on the Workflows associated to them. But you cannot change the Statuses to which the issues can be set, nor how they can be changed from Status to another Status.

[Jasdeep Joga]

Thank you, for your support.

I have one more question, I was able to setup 2 separate boards under 1 project and both have different statuses as part of each of their workflow but under the drop down option where you see the issue transition all workflow fields would appear instead of the ones that the board has.

That limits the status change transition to just sliding the issue through the board instead of using the drop-down option and when 2 teams are working on 1 project they might accidentally choose incorrect drop-down option that would take away the the issue from their view. Is there a way to stop that from happening? 

[Trudy Claspill]

Hello @Jasdeep Joga 

The Status change drop down will show all statuses/transitions that are valid for the issue and available to the user based on the workflow used by the issue type.

It is possible to modify a workflow to hide transitions from users by using Conditions. That would affect the users everywhere that the issues they work with use that particular workflow. The affect would not be limited to when they are viewing the issues through a particular board.

https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/#Conditions

If the workflow is shared by multiple issue types, then all issue types that use that workflow would be affected.