What is a simplified Jira workflow?
In most Jira projects, work items move from To do to Done through a workflow. Each workflow is composed of statuses and transitions that work moves through, usually representing a process in your organization.
When a Software project is created with a Scrum or Kanban board, it uses a simplified workflow instead. Simplified workflows allow workflow management to be delegated to the administrators of the board. For example, board admins can add columns (i.e. statuses) to their board, without needing to contact a Jira admin.
Simplified workflows and Jira workflows compared
Simplified workflow | Jira workflow |
|---|---|
Statuses can be edited in Board settings.
| Can only be edited by a Jira admin in Jira settings. |
| Has more steps than are typically needed on a board (see the default Jira workflow). |
Allows issues to be dragged freely between columns | Has workflow "conditions" that prevent issues from being dragged freely between all columns |
Displays no screens on any transitions, all transitions will happen instantly. | Displays screens for Resolve issue, Close issue, and Reopen issue. |
Automatically sets a resolution of 'Done' when issues are transitioned to the 'successful' column, i.e. statuses mapped to the successful column (see Configure columns) | Resolutions aren’t set automatically, but this can be configured. See [link] |
Can be edited via board settings or directly on the board (provided you’re a project admin for the project used by the board, or a board admin for the board itself) | Can only be edited via workflow configuration, see Workflows for more information |
Was this helpful?