-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
6.0.6, 6.6.70, 6.6.80
-
Standalone JIRA 5.1, Tomcat, JDK1.7, Ubuntu 12.04
-
6
-
The workflow we use for Scrum adds an additional "Verified" step after Resolved, and the columns on the Rapidboard are set up to have In Progress and Resolved as partially complete, followed by Verified as the state for the "Done" column.
There is no direct transition from In Progress to Verified, requiring two steps to move from In Progress to Resolved to Verified. However, when all subtasks are complete on a story (that is, in the Done column), the "Move to Done" transition button appears even though the parent Story is still In Progress.
Attempting to click Move to Done brings up a lightbox indicating there's no valid transition.
We can easily workaround this by moving the Story to Resolved first, but it seems like there's a better experience that could be put together.
This seems to relate potentially to GHS-6063.
It should be possible to set the behaviour of the parent story to one of the either:
- be able to pre-select the status that a parent should be transitioned to when all subtasks are complete;
- disable the automated parent transition altogether.
- relates to
-
JSWSERVER-10506 Do not show Move to Done Button for users without Permission to Move to Done Column
- Closed
[JSWSERVER-6499] "Move to Done" button appears regardless of whether the transition is valid
Raj Adluru
added a comment - this is not resolved, we still get this JIRA v7.2.1 and JIRA agile v7.2.8, not sure why this is shown on agile board!
Raj Adluru
added a comment - this is not resolved, we still get this JIRA v7.2.1 and JIRA agile v7.2.8, not sure why this is shown on agile board! 
Marketa Dvorackova
added a comment - Same issue here. We have the parent following a different workflow than the children. So when all the children are Resolved, that doesn't mean that the parent is resolved. In our case it goes to testing first. So I join the party saying : it should be checked before you offer a button for something that can't be done.
In any case happy to see that it is planned to be resolved. Thanks.
Marketa Dvorackova
added a comment - Same issue here. We have the parent following a different workflow than the children. So when all the children are Resolved, that doesn't mean that the parent is resolved. In our case it goes to testing first. So I join the party saying : it should be checked before you offer a button for something that can't be done.
In any case happy to see that it is planned to be resolved. Thanks. 
Kevin Howe
added a comment - We're seeing this issue too, when clicked the button says:
All sub-tasks for parent issue ISSUEKEY-1 are now Done. However, the parent issue cannot be moved into the Done column as there are no matching transitions.
Which shows that JIRA is aware that the issue cannot be transitioned to Done.
This issue should be solvable simply by applying the same logic check to the button so that it does not show at all in this scenario, only if the Story has the ability to be transitioned to Done.
Kevin Howe
added a comment - We're seeing this issue too, when clicked the button says:
All sub-tasks for parent issue ISSUEKEY-1 are now Done. However, the parent issue cannot be moved into the Done column as there are no matching transitions.
Which shows that JIRA is aware that the issue cannot be transitioned to Done.
This issue should be solvable simply by applying the same logic check to the button so that it does not show at all in this scenario, only if the Story has the ability to be transitioned to Done. 
Not resolved on Agile Cloud at this time