Configuring 'Move to Done' on Kanban board with swimlanes

Kerrie
Contributor
November 9, 2023

On our kanban board there is a 'Move to Done' button when all of the subtasks are complete:

Capture3.JPG

 

Typically the next stage when the dev subtasks are done, is for the parent ticket to go in to testing, however the only option here is to move it to Done. 

We would like to be able to configure this button so that rather than moving the parent to Done it moves it to the next workflow status, which in our project is Ready for QA

It would appear that this is not an option 

Automation will not work for us as the developers need to complete a build first, often they wont do this until a number of tickets are ready, and so we need control over when we move it to Ready for QA 

Are there any other options to achieve this? Could this be logged as an Enhancement Request to make that Button configurable? 

2 answers

2 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 9, 2023

Hi Kerrie,

There's no way to do this.  Jira has no way of knowing what you intend to do with an issue next.  It can only do "move to done" because done is an absolute decision to finish the issue.

Kerrie
Contributor
November 9, 2023

Yes I realise it doesn't do it at the moment,  however if it was configurable then you would tell it what you want it to always do next. I was advised by Atlassian support to log this so they can add it as an enhancement and to see if anyone has any other bright ideas as workarounds I can use for the time being 

1 vote
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 9, 2023

Hi @Kerrie 

As Nic noted, that button cannot be configured.  And you describe some of the team's workflow with build management and bundling of issues. 

Has your team considered trying the DevOps features / integration with your Jira project?  That may enable using automation rules, triggered on the pipeline operations, to transition your user stories.  Please look here to see example rules and information on those trigger types:

Kind regards,
Bill

Kerrie
Contributor
November 10, 2023

Thank you! I will look in to that :) 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events