platform-guideline 1 linked patterns checked
Atlassian Support: Configure columns in Jira Cloud
Documents Jira board columns as work item status containers, default Kanban columns, column add/delete/rename/move behavior, status-to-column mapping, constraints, and right-most done semantics.
Read with a purpose
What this source can teach
Use this source to understand a platform convention and the setting it was designed for.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Kanban board | Choose Kanban board when work items progress through shared workflow states and column movement is the primary interaction. | Each column represents a workflow state or selected column field value, and moving a card updates the same value shown in details, reports, and automation. | Atlassian documents board columns, default Kanban states, status mapping, column constraints, and right-most done semantics. |
Comparisons supported by this source
- Kanban board vs table vs calendar view vs list view
Atlassian documents column status mapping, column editing, constraints, and done-column semantics.
Evidence Role
This source is treated as platform-guideline evidence. Its value comes from the specific claims and setting described above.
Publisher: Atlassian Support. Last checked: .