-
Suggestion
-
Resolution: Unresolved
-
None
-
7
-
10
-
Problem Definition
As a configurer of an Agile board, similar to how I can configure my custom issue statuses to belong to one of the three options, I would also like to configure the columns on my agile board to be:
- Not Started (To Do)
- In Progress
- Done
Currently the automatic assumption is that the very left column is Not Started and the very right column is Done.
This is a huge limitation in Jira Agile and causes problems especially with rendering the burndown chart.
I do not believe that asking the user to merge multiple of my columns into one or to create a separate Agile board is a sufficient solution for the issue.
Suggested Solution
Allow the ability to add additional columns to also represent Not Started (To Do) and Done in addition to the ability to already add an In Progress column.
Note
Judging from the comments on GHS-10261 and GHS-11355 as well as this post on Atlassian Answers, I do feel that this is a feature of general interest.
Please stop closing every suggestion about this as "Answered" and leave any one of these three open for us to vote on.
Note: I am explicitly filing a duplicate of GHS-10261 and GHS-11355, both of which I find to have been closed prematurely.
- is related to
-
- Closed
-
- Closed
- relates to
-
JSWSERVER-3138 Bug in Burndown Chart - Tickets with Status' placed in "Done' column under Task Board Do Not Reflect in Burndown Graph
-
- Closed
-
-
- Gathering Interest
- was cloned as
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-12169] In Configure Board, allow multiple "Not Started" (Blue) and "Done" (Green) columns
I would appreciate it either as it would help us to align Jira to our definition of "done"
This is more or less already a feature in Board Settings > Columns, and to modify it in the way this ticket is asking for sounds like it would be an operational headache as a workflow. (Aside: the To Do column is currently grey – not blue – and the current version of the product supports multiple blue columns in the workflow between To Do and Done)
The first column in your board settings will always be Grey / To Do, and the last column will always be Green / Done. You can add multiple intermediate columns (blocked, in progress, in review, whatever) in between that are blue.
Within any given column, you can have multiple statuses. To put multiple statuses into your Done column, you just need to drag and drop the desired statuses from the Unmapped Statuses column into the Done column (or any other column representing that stage of your workflow that corresponds to a given status).
When you're moving things across your kanban board, columns with multiple mapped statuses will give you a visual indicator of where in the column to drop the ticket to put it into a specific status within that column; by the same token, changing the status within a ticket edit screen will move it to the mapped column on the board. Things are either done, not done, or at some in-between stage, and the board supports that. Something that is To Do isn't done, and something that is Done is done – anything that falls outside of that category should be in a blue column in between. If you want to further filter the To Do or Done columns (I mostly only see value in doing it for the To Do column in aiding selection from a large number of prioritized tickets), then you can easily set up Quick Filters to filter the board to view the subset of statuses you're looking for.
+1 We have three different flavours of Complete:
"Closed - not a valid issue",
"Closed - no longer required",
"Closed - implemented".
I made the stupid decision to use a Next-gen project for a large software product. Now 1600+ tickets in, various third party integrations with JIRA and loads of automation rules configured, it is not feasible to migrate to an old-gen project.
I'm using cloud and I'd love to see this. Our workflow indicates two "green" (done) columns, one for done-but-have-remarks-for-others while the other is done-and-forget (all remarks are discussed with ppl of interest). Some issues moves directly to latter, and some are first resolved into former and than moved to the latter column, usually on the end of the sprint (retro). Both of columns indicates that issues are, technically speking, done.
+1