Need support with automation rule

Question

I need help building a Jira Cloud automation rule.
• I have two issue types: Task and Instance. (Both issue types are from different projects)
• Both have a multi-select field called "Subsystem".
• Linking rules in our project are:
• Task → Instance uses link type has defect.
• Instance → Task uses link type is a defect of.

Requirement:
Whenever a Task and an Instance are linked, the value of Subsystem from the Task should always overwrite the Subsystem in the Instance.
• This should work no matter which side the user starts from (Task or Instance).
• Even if the user mistakenly uses the wrong link type (reverse the link type), the rule should still ensure Subsystem is always copied from Task → Instance (never the other way).

Note: When user uses proper link type then subsystem value from instance is updating with the value from task issue type.

When user reverse the link type then value from task is updating with a value of instance which is not correct.

Thanks,

We are using Jira cloud

Prathap DL_66helr · Answer

Hi @Bill Sheboy  I found the solution.

I just added condition to check the issue type is equals to Instance and it worked.

Thanks for your support.

Prathap DL_66helr · Answer

Hi @Bill Sheboy  could you please share the automation rule? I'm not aware how to use branches in rule.

Bill Sheboy · Answer

Thanks for that information, @Prathap DL and what you show is puzzling to me.

My understanding is when a link type is directional, rules with a Work Item Linked trigger always run in one single direction, regardless of on which work item the link was added.  Your rule appears to show something differently...or the link type used does not have a defined direction.  Regardless of that...

For your scenario, you want the update to be on the Instance work item, regardless of link direction used.  Thus, the rule could use an if / else block condition to test the trigger work item's type and then branch to the correct work item for the two cases:

* branch to the destination work item and copy data from the trigger one, or
* branch to the current (i.e., trigger work item) and copy data from the destination one

For that second case, you may need to use the Lookup Work Item action with JQL to get all the destination one's data for use in the edit.