Hi, I'm trying to achieve the following using automation.
I am the administrator of Project Acme. Issues can be linked from other Projects.
I have created a new issue IS-11 in Project Acme. In IS-10, I have created a new subtask IS-101.
On IS-101, I have linked another issue from another project: "IS-101 is related to XY-01"
What I Need
As soon as I link XY-01 on subtask IS-101, XY-01 should also get linked to the parent issue IS 10 with specific relation.
So automatically create relation "IS-10 is blocked by XY-01" when XY-01 is linked on subtask IS-101.
I only have access to Project Acme and I can create rule for the same. The Trigger "Issue Linked" is only triggered when IS-10 is linked on other project. It will not be triggered if an issue from another project is linked on IS-10.
So even if I have "Destination Issue" branch, the rule never triggers when an issue is linked.
According to https://support.atlassian.com/jira-software-cloud/docs/automation-triggers/ "Issue updated" or any other trigger is not executed when an issue is linked.
How can I trigger a rule when an issue is linked? Alternatively how can I achieve the need?
can you change the rule actor to an acccount, thas hat access to all the projects.
maybe your jira admins can create a dummy account in the local jira directory for this purpose.
in my jira instance, i only use dummy accounts for the automation rules, so that the users can see that the issues were change by an automation rule.
I understood it in a way that at least two projects are involved (IS and XY).
I was able to reproduce the general idea of an automation rule towards this but, however the link is only made to the "destination issue" on trigger event - which is in that case the sub-task.
There is no option (at least not that I would have seen it) to execute the rule on the parent issue of the destination (linked issue).
I reproduced it on my instance by building a rule for the scenario.
The showstopper is that the rule is executed against a branch - which in your case is always the sub-task.
It was not possible to link the story to the parent of the sub-task.
The parent issue in that case is the one which holds the sub-task. From Automation's perspective the issue (including the sub-task) is referred to as "Destination", though.
All the tests were based on the guide here:
The output looks like the following from logs:
Overall I believe in that case one is running into the limitation:
Branches are isolated
Any changes that occur in a branch will not be visible to the main branch or other branches.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event