Simplfied workflow: complete sprint w/ in-progress issue in done column shall move issue to backlog

[Thomas Lehmann]

We've a simplified workflow setup where an "in-progress" status (yellow) is mapped to the "done" column. The "Set resolution" checkbox is not ticked.

The rationale behind that status and mapping was to keep issues with completed development and testing but pending release in the sprint and carry them into the next sprint for a scheduled release (they shall not disappear and remind us every day that there is still work to be done). To save horizontal space we decided having that status in the existing "done" column instead of a new column.

See this board config:

(Find "QA done" in the right most column "done" and status "type" "in-progress", yellow.)

When completing the sprint, the issues with status "QA done" are not moved back to backlog (or into the next sprint) instead they're closed (or whatever). We expected them to move to the backlog (or new sprint for that matter).

It looks like JIRA/Greenhopper is treating the column "done" as "completeness" indicator, not the actual status itself.

Is this the expected behavior? Is there anything we can do to carry the issue to the next sprint (or to the backlog), if yes, how should we configure our board?

[Nic Brough -Adaptavist- · Accepted solution]

Yes, that is what should happen.

The column on the far right is "done".  It represents the end of the process, where issues need no more attention.  Anything in the "done" column is done, so it won't go into the backlog when you end the sprint.

You've chosen to tell Jira that the status resolved, closed, live and qa status are "done".  I suspect you might want to put QA in a different column.

[Mirek]

JIRA treat everything on the right most column as Done even it is not a "green" status. Looking at your screenshot I suggest you to completely remove QA Done. If the issue is in QA then if someone moves the ticket to next status it is automatically an information that QA is already done (or at least your team should be aware of this). It is similar like moving from "In Progress" to "Resolve". You do not have any middle statuses like "Progress Done"