As a project admin

I want the board settings, column mapping to validate a status value's category matches what the columns represent

So that my boards are consistently defined for reporting and maintenance

 

Acceptance criteria

• when mapping a status to the board, only ones with the "To Do" status category can be mapped to the leftmost column
• when mapping a status to the board, only ones with the "Done" status category can be mapped to the rightmost column
• when mapping a status to the board, only ones with the "In Progress" status category can be mapped to the middle columns
• when mapping a status to the board and the status category does not match the designed target status category, an error shows during an attempt to map the status
• Bonus: make this validation optional so teams can incrementally improve their boards over time

Business case:

There is a lot of community confusion over having status category be unrelated to the mapping of columns to a board.  The inconsistency that allows status values to be mapped to unrelated status category columns leads to confusion when Jira reporting and Sprint behavior are out of alignment.  Others have posted in community forums this "flexibility" helps with the reuse of status values between different workflows, boards, etc.  If that were in fact the case, then the Status Category attribute would not be associated to a specific status: instead it would be associated to a status-board pair.