2 boards, 1 project -> can i separate the statuses?

[Stefannie Tan]

the 2 boards is because there are 2 teams. 1 is doing scrum and 1 is doing kanban. but the project is the same. however, obviously the workflow will be different, so is there a way for me to separate the statuses displayed?

thanks for any suggestions!

[Trudy Claspill]

Hello @Stefannie Tan 

Can you provide more information on how the workflows are different?

Only one workflow can be applied to a given issue type in a given project. You can't have different workflows for a single issue type in a given project.

You might have Conditions on the transitions in a workflow such that some transitions are not visible based on data elements in the issue (like the value of a "team" field).

In a board you can choose to move statuses to the Unmapped Status section of the status/column mapping. If you do that, issues in those statuses will be hidden from the board. But that will not block somebody from setting an issue displayed in that board to one of those statuses.

[Stefannie Tan]

@Trudy Claspillhi trudy! sorry for the late response. one board is using scrum, and the other kanban, so the two teams are both using different statuses.

[Stefannie Tan]

i guess one way is to add additional statuses for the other board to use exclusively.

[Trudy Claspill]

The available statuses are not based on whether a scrum board or kanban board is in use. A board is just a way to visualize and manipulate issues that exist in 1..n projects. Boards select the issues they contain based on a filter used by the board. The statuses available on the board are based on the issues that are in scope for the filter and the Workflows that have been applied to the source project(s) for the types of the issues that are in scope.

If the teams are using the same types of issues from one project, then both boards will show the same available statuses.

If you want the teams to have different types of statuses they either need to use different types of issues from one project or use different projects.

[Stefannie Tan]

1 project can't have multiple issue type schemes, which was what i had wanted to do in the first place.

"if you want the teams to have different types of statuses they either need to use different types of issues from one project or use different projects."

-> i wasn't aware that they had to use different issue types to have different types of statuses. i will try out some combinations on a test board i created for this purpose.

[Trudy Claspill]

It is true that a project can have only one Issue Type Scheme. That defines the types of issues available in the project.

And a project can have only one Workflow Scheme.

However, within the workflow scheme you associate a Workflow to an issue type. The Workflow determines the statuses that are available for that issue type. Within the Workflow Scheme you can associate different workflows to different issues types. So, if the teams use different issue types then they can have different workflows/statuses available to them.

[Stefannie Tan]

@Trudy Claspillsorry, it can get confusing for me.

ok, so if i understand it correctly, one project can have multiple Worklows, but the Workflow 1 and Workflow 2 should have different statuses/issue types?

Is that right? I thought I could use the same issue type but have it under a different workflow and a different status.

[Stefannie Tan]

originally, i have 2 teams who work in different ways but on the same project.

1 is kanban, and the other is scrum.

But since they are working on the same product, I had wanted them to have just one backlog, but still be able to work the way each team wants to work.

But it seems that I would need to add more issue types just to let this happen and have each team have their own workflow without affecting the other?

Is that right? Thank you!

[Trudy Claspill]

ok, so if i understand it correctly, one project can have multiple Worklows, but the Workflow 1 and Workflow 2 should have different statuses/issue types?

Is that right?

Correct. If you want each team to have different status for their issues but work from one project, that requires the teams to use different issue types. 

I thought I could use the same issue type but have it under a different workflow and a different status.

If you want them to use the same issue type but have different statuses, the teams would have to use different projects.

originally, i have 2 teams who work in different ways but on the same project.

1 is kanban, and the other is scrum.

Do you show all issues in both boards? How do the teams know which issues belong to which teams? Do they decide that based on the summary and description, or do you use some field to specify which team owns the issue?

Why do the teams need to have a shared backlog? Is it because you want one backlog for the product being worked on?

But it seems that I would need to add more issue types just to let this happen and have each team have their own workflow without affecting the other?

Is that right? 

Correct. If you want the teams to work from issues in just one Jira Project but have different issues statuses and workflows, then you would need to have them working on different Issue Types in that project.

[Stefannie Tan]

@Trudy Claspillthank you so much for the detailed answer!

Do you show all issues in both boards? How do the teams know which issues belong to which teams? Do they decide that based on the summary and description, or do you use some field to specify which team owns the issue?

yes. the teams are working on different components of the product, but they still need to collaborate with each other on parts.

Why do the teams need to have a shared backlog? Is it because you want one backlog for the product being worked on?

yes, it's one product, so I would prefer them to have one shared backlog.

personally, i think for simplicity's sake, it might be better to have a different project but have that project's board displayed in one place. but with a little work, there's no reason i can't have them both on the same project. I just need to separate the Workflow and Issue Types.