Hi all,
tried to get a scripted JQL condition working, but i have some problems with that setup. Here´s the use case:
Workflow A has a post workflow action which fires after all other actions:
Transition 41 will be triggered on all issues linked to the current issue through the has Epic link type.
Workflow B (which is basically a copy of A) is acting as expected, so far all is ok. But, while adding a single condition in workflow B to only allow this transaction when:
Script workflow function : The action will be allowed if the issue matches the JQL query: "project = "COPY Way Forward" and issuetype = Epic and issueFunction not in linkedIssuesOf("Status != Closed", "has Epic")"
Logically this is correct, checked it in parallel in the issue search (only when all linked issues are closed the according epic is shown in the result, otherwise not; Condition Validator plugin also confirms this).
The idea behind this additional condition is to not allow this triggered transaction when at least one issue linked to the epic is not in status closed. I assume that the update of the issue in workflow A is not fast enough to pass the condition build in workflow B, but how to achive this goal?
Any ideas are welcome!
Thanks & regards,
Hans-Hermann
Community moderators have prevented the ability to post new answers.
@Jamie Echlin [Adaptavist]: Do you got an idea what might going wrong here?
The only workaround i know is to create an automation rule where to check regularly the same conditions and update the issue (in my example it would be the Epic to be closed if all linked issues are closed).
Thanks for any hints!
Regards,
Hans-Hermann
I've had issues sometimes when using these advanced queries in places other than the issue search. Have you tried saving that query as a filter, and doing "filter = myfilter" as your query in the post-function?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nicolas, did a quick test, the behavior is still the same as before. Nevertheless, thanks for your answer!
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.