You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
On our kanban board there is a 'Move to Done' button when all of the subtasks are complete:
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?
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.
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
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: