I'm afraid I do not know what "search engine syntax and syntax used in a validator are the same or different?" means.
To prevent a transition, you should usually use a "condition". In your case, the condition needs to be placed on the transitions for the parent type and the pseudo-code for such a condition is roughly:
Note: I don't know how you are representing "cloner", so I have taken a complete guess at it being an issue link to another issue.
Before I try to expand that into any form of real code, does it make sense? Have I got the right idea about what you're trying to do?
This is our workflow for parent issue
And this is postfunction for parent issue (transition from column 2 to 4 from the first picture)
That is how it looks on the board (on the 4th column it creates a cloner)
In this screenshot you can see how this clone looks in parent issue
And this is a clone
But without code condition I can't prevent transition of parent issue to the next step (5th column) if linked issue (cloner) isn't closed. You can see it below
I have two workflows for one project (different workflows for different issue types (parent and cloner)): one of them is for issues in parent process and the second one is for cloners. When parent issue is going to the step in the 4th column, it makes clone (issue with another workflow), but condition for parent issue transition to 5th column is that this clone must be in "closed" status (done) in it's workflow.
Ok. So you need a condition on the source issue workflow that can execute the a coded version of the pseudo-code I gave earlier. Are you using Script Runner for this, or something else?
Also, I've talked about "source" issue here because in JIRA-speak, "parent" suggests sub-tasks, not clones.
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot