I have created a custom workflow and added conditions to one of my transitions. I have an issue that uses this workflow and I cannot transition to one of the states; it's not available in the issue screen. I am assuming this is because one of my conditions has not been met. However, I think all the conditions have been.
Is there a way to determine which condition has not been met on the issue?
Actually, I think I know what the transition condition is. We also use Fisheye/Crucible and the issue is currently in a "In Review" status. In order to transition to "Review Complete" status we have theses conditions:
Transition to execute only if there are no related open Crucible reviews.
Transition to execute only if there are no unreviewed changesets related to this issue.
There is a commited changeset that has no files in it (merges a branch back into trunk). This shows up as an unreviewed commit in the JIRA issue's "Source" tab. However, even if I create and close a review on that changeset JIRA doesn't pick it up. So, I can't transition to "Review Complete".
We're using this same check, as it's a nice check to have, but Developers are complaining because there is no feedback. Is there any chance that Atlassian will consider adding some visual feedback so users know why an issue cannot move forward? Seems counterproductive to have a feature that blocks a workflow move, if no one understands why it's blocked.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs