Hi Atlassians,
I am using the Automation plugin for many things and generally it works perfectly, but I have hit a strange situation:
Rule 1: A manual rule that raises a Change issue in a ServiceDesk project and links to the triggering issue
This works fine, I use a condition as follows to stop multiple Change items being created:
First value: {{#issue.fields.issuelinks}}{{outwardIssue.fields.summary}}{{/}}
Condition: Does not contain
Second value: 'AutoCR:'
Rule 2: A state transition rule that does the same Change issue raising as above, using the same compare condition so a Change is NOT created if one exists with that summary term...
THIS DOES NOT WORK
I put an interim comment adding step into the second rule to dump the inward and outward issue link summaries and they do not appear. The data DOES appear if I do the same in the first rule... So the second rule seems to have a different object represented by 'issue'
Things I have tried:
- inward vs outward issue links
- issue vs triggerIssue as the object to check
- Check the JSON via a REST call
I cannot work out why these issueLinks don't seem to exist on the issue object in a state transition rule, versus a manual rule...
Any help gratefully received!
Simon
OK,
So the answer was to use the 'Related issues condition' and match on the linked issues NOT matching a piece of JQL e.g. project = ServiceDesk and issueType = Change
Much neater than messing with summary pattern matching, although still not sure why that was an issue...
Automation plugin rocks!
Si
Hi Simon,
Great to hear you already solved this one yourself! Yeah the related issues condition is much easier for this case.
I think the underlying cause might be that for the issue transitioned rule, we transform the underlying issue event object Jira passes to us (which I'm guessing doesn't contain issue links), however the manual rule, does a lookup of the issue object which would contain the issuelinks. The related issues condition also does this lookup (via JQL search).
Cheers,
Andreas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.