Only Display Workflow Status Buttons/Selections on Issue if that Status is Mapped to Scrum Board?

[Katrina Thacker]

Is there a way through workflow properties or Behavior scripts or other to do the following:

• Sample Workflow is Open, In Progress, Blocked, Ready for QA, PO Acceptance, Failed QA, Closed
• The Sample Workflow is an Open Workflow meaning all transitions are allowed - there's no transition restrictions (e.g. like the Software Simplified Workflow)
• Sample Workflow is used by all teams/projects (to make it simple let's say we have only two teams/projects in Jira)
• Team A: They have all statuses mapped to their Team A Scrum Board
• Team B: They don't have a need/desire to use PO Acceptance so that status is Unmapped for them

My desired user experience:

For Team A, when someone opens a user story ALL the workflow status values are available via buttons or in the workflow pull down menu

For Team B, when someone opens a user story they see all statuses EXCEPT PO Acceptance because it is not a mapped status for their Scrum Board

Is this doable?  Thanks in advance for your help! 

[Boris Berenberg - Atlas Authority]

No, it is not, and the reason why is because you're thinking about how this data maps together incorrectly.

A board is purely a view on issues. A given issue can exist in many boards. What would you do if one board has one status on it, and the other board has another status. 

[Katrina Thacker]

I don't believe I'm thinking about it incorrectly, just differently. ;>

Your question about about one board with one status and another board another status I'm not sure I get your meaning.   In short, what I believe your response is telling me is that there's no way to 'query' if you will whether a status exists on a scrum board for a project and use that to control whether or not the workflow transition button should be displayed on an issue in that project. 

[Boris Berenberg - Atlas Authority]

You're getting the right answer for the wrong reasons. It's like doing faulty math and then guessing correctly on the multiple choice answer portion.

Think of it like this:

• A project contains issues
• A board contains issues
• A board does not contain projects
• A project does not contain boards (the UI will fake this one which is why users get confused)

Hence you can't attach project specific logic to a board or the other way around.

What this means for your example is that you want an issue with a workflow condition (how you hide transitions) which exists in a workflow which exists in a project to access board information. But I can have 100 different boards all including that issue, so which board should it be accessing? Does that make more sense?