Map multiple Jira statuses to one column
Map several workflow statuses to one board column when the team needs a simpler view of progress. For example, a Review column can contain both Code review and QA. The statuses still exist separately in Jira.
Map statuses to columns
A board or space administrator can adjust the board’s column mapping.
-
Sketch the intended board
Write down the status-to-column pairs before editing. For example: In development → Doing; Code review → Review; QA → Review; Done → Done. -
Open the mapping settings
Open Board settings → Layout → Columns and find the status mapping area. -
Place the existing statuses
Move Code review and QA into Review. Map every status that should be visible. Changing this view does not merge the underlying statuses. -
Verify a card from each status
Confirm both kinds of work appear in Review. Open each card to verify its status. Also check a card moved into Review: the workflow and available target statuses determine the transition.
Map field options across spaces
Use BetterBoard’s column mapping to bring different field options into the same board columns.
Use the space’s Columns and statuses settings to manage mappings.
-
Open the board settings for the space
Go to Space settings → Board → Columns and statuses. Work with a space administrator if these settings are unavailable. -
Prepare the target column
Create or choose Review. Creating a column here does not itself create a workflow status; use the workflow editor when a new status is actually needed. -
Assign the statuses
Assign Code review and QA to Review. Keep the existing statuses rather than replacing them with a single name just for presentation. -
Check the completed-work boundary
Ensure completed statuses sit in the appropriate completion column. Review the board with one example from each status before announcing the new layout.
Map field options across spaces
Use BetterBoard’s column mapping to bring different field options into the same board columns.
Good to know
Example: the board can simplify a workflow without hiding the underlying distinction.
- A developer can still search for Code review while a tester searches for QA, even though both appear in Review.
- An unmapped status can hide its cards. Check missing items after any mapping change.
- A column is a presentation choice; a status is stored on the work item. Renaming one is not a substitute for changing the other.
- Grouping by assignee or priority is a different task. Use the grouping guide if you want lanes organized by another field.
Map field options across spaces
Use BetterBoard’s column mapping to bring different field options into the same board columns.
FAQ
Does mapping change all existing work item statuses?
No. Mapping determines which column displays a status. Changing workflow statuses is a separate operation.
Can I use this across spaces?
For a board containing several spaces, account for the statuses used by each workflow. BetterBoard documents field-option mapping across spaces; see the linked setup instructions.