Use JJUPIN. We have a similar recipe here; you need to modify it. See also Nic's answer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's a similar principle, except you look for links instead of subtasks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You'll need to find or write some code that can do that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I understood this in the search process. Where can I look for codes to at least understand the principle? search engine syntax and syntax used in a validator are the same or different?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is our workflow for parent issue
1.png
And this is postfunction for parent issue (transition from column 2 to 4 from the first picture)
3.png
That is how it looks on the board (on the 4th column it creates a cloner)
5.png
In this screenshot you can see how this clone looks in parent issue
6.png
And this is a clone
9.png
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
33.png
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, I can't make out what you have tried to do from those. Only one of them is of the workflow and it looks like it is cloning the current issue correctly, but there's nothing about the conditions you need on the workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, Nic, we are using Script Runner, JIRA ver.6.1.7. And thanks a lot for clarification about "source" issues! Hoping for you help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nic, do you have some idea for our case?) Can you tell me, where I can find more information about jql queries? examples may be
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
JQL has nothing to do with this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.