I am trying to create a condition in my workflow that will not allow the issue to be closed if it has linked issues that block it and don't have the status Closed. The background is that I am using the plugin Structure to arrange my issues. Using the Sync feature when I structure my project it adds blocked links to the issues. So I want to make sure that a parent issue can't be closed unless the child issue is closed.
I have played around and checked the forums but am not having much luck with this.
I have attached a screen shot of my latest attempt.
You have to check "Issue link types not selected are allowed" and "Issue types not selected are allowed". I add some screenshots using "Validation on linked issues" instead of the "Condition on linked issues", since both modules use the same configuration.
Fidel Castro Armario.
I am using Jira 5.0.3. I am not able to see the above screen, when I try to add a new validation. How to get to that screen? where I can add " Validation on linked issues ".
When I try to add all i can see is the following features.
user permission validator
Do i need a plugin for that ? if so what plugin is that.
We have configured Preventing parent issue from being closed until child linked issue status is closed using "Jira Workflow Toolbox" plugin. It is working perfectly. Now we need to send email notification whenever a user want to close parent issue without closing child link issue. I.E - test1 is parent issue and test2 child issue. If anybody try to close test1 until closing test2 then a email notification should be generated like - "Linked issues must be closed before closing parent issues". Also please note I am not talking about subtasks. The issues are normal tasks but linked
JIRA Workflow Toolbox doesn't have any post-functions to send email notificacions.
Anyway, if you are using validator "Validation of linked issues" you are already showing the user a custom message informing him he should close child linked issues before closing parent issue. This is not the case for "Condition on linked issues", so I usually recommend to use validators for this kind of usage.
In your case, who do you want to send the email notificacition to?
In our case the requirement is as below -
when somebody try to close parent issue without closing child link issue a mail notification should be send to certain jira group members.
Also "Validation of linked issues" is not working for "Start Progress" transition. We need to configure this for "start progress" transition. I.E - test1 is parent issue and test2 child issue. Noybody can start progress test1 until start progress test2. However this is working for "Stop Progress". Could you please suggest
You shouldn't have any problem to make it work on any transition of your workflow, even on "Create Issue" transition.
Please, attach a screenshot of the configuration you are trying in "Start Progress" transition, or send it to me by email to firstname.lastname@example.org.
Which issue link type are you using to set parent-child relationship between issues?
Do you want to set the restriction you described, only for issues linked with issue link type "has to be done after", or do you want to apply them also to issue link types "duplicates" and "depends"?
In first case, you have to uncheck issue link types "duplicates" and "depends". If you want to apply the the restriction to all three issue link types, keep them checked.
Inward and outward are both directions for a same issue link type. For example, when you link two issues (A and B) using issue link type "duplicates / is duplicated by", if you look at the link from issue A you may see "A duplicates B" and when you look at the same issue link from B, you see "B is duplicated by A"
When configuring the validator, you can see that every issue link type has one check available at parameter "Inward issue link types" and another at parameter "Outward issue link types". If you need to configre the validator for all issue link types, you have to check only one of the directions for each issue link type. You can choose any of both directions available for each issue link type, but never both, since if you checked both directions for a same issue link type, you would be losing the sense of parent-child relationship, and the validator never would be satisfied for that particular issue link type.
For this reason, it doesn't make sense to configure the validator for issue link type "relates to", since both directions are equally named, making it a no-directional issue link type, and so there is not parent-child relationship.
We have another requirement regarding this. when somebody try to close parent issue without closing child link issue a mail notification should be send to certain jira group members. Could you please inform whether this is possible or not? If possible then could you please provide us the procedure?
Sorry, JIRA Workflow Toolbox doesn't have any post-functions to send email notificacions. Anyway, you are trying to send a notificacion when a transition can't be executed due to a validator failure. Not even a post-function would solve your requirement, since the post-funcions won't be executed.
At this moment, the plugin can't fullfil this requirement.
I have documented a similar use case in detail: "Automatically move issue to "In Progress" status once all its blocking issues are in "Closed" or "Resolved" statuses"
Please, pay attention to:
Have you tried adding the Condition "Sub-Task Blocking Condition" with "Closed" status?
You should end up with the following condition on your transaction "All sub-tasks must have one of the following statuses to allow parent issue transitions: Closed. ".
Hope this helps,
I have a post function setup on the resolved transition to auto-transition blocked issues to unblocked/open when the blocking issue is resolved/closed. I am trying to add a validator that won't allow the blocked issue to transition to unblocked/open if it has multiple blocking issues and one of them is still open. The validator works when I go to the issue and click unblocked, I get the text I entered in the validator if there are still open blocking issues and I can get it unblocked if all blocking issues are closed/resolved but the post-function does not work. Is there an order that these fire in that is causing the issue here?
Example: Bug A is blocked by bug B & C. Bug C gets resolved, post-function should try to unblock/open bug A but validator should see that bug B is still open and stop it. (working) Once bug B is resolved and assuming bug C is still resolved then the post-function should fire and the validator should pass and bug A should transition to open. (not working)
Any ideas what is causing this to fail?
Hi all! My name is Miles and I work on the Marketplace team. We’re looking for better ways to recommend and suggest apps that are truly crowd favorites, so of course we wanted to poll the Community. ...
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