I am creating custom workflow for my organisation and would like to prevent moving issue from "Selected for Development" into "In progress" if there does not exist at least one branch for that issue. I've already created the trigger which automatically moves the task into "in progress" as soon as branch is created, but I would like to prevent developers to manually move the task into "in progress" if branch does not exist, however if it exists then I would like to allow manual movement. Is there something like "branch exists condition/validator"? I do not see something like that in my JIRA options, however similar use case is described in JIRA advanced workflow configuration documentation, so I guess something like this is possible.
For the time being, I've made a workaround:
- on transition from "selected for development" into "in progress" there is a condition that task must have previously been "in progress"
- when branch is created, trigger automatically moves the task to "in progress"
Thus, task can move into "in progress" first time only by creating a branch.
Unfortunately, this workaround does not work for cases when developer creates branch before task is moved in "selected for development" state. This can be further worked around by adding another transition with same trigger (from "backlog" to "in progress"), which cannot be performed manually, but this is a dirty hack and does not allow checking for required conditions.
A condition "branch exists" would be much better solution.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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