Add Participant to linked items

[Darryl St_ Pierre]

Trying to create an Automation for when a work item from Project B is linked to a work item in Project A, a Request Participant is added to the Project B item. Created this basic automation but it's not even executing when I link a ticket from within Project A.

What am I missing?

[Trudy Claspill]

Hello @Darryl St_ Pierre 

What is the Space Scope for your rule? It will need to be a multiple Space scoped rule identifying both Project A and Project B as in scope. Only Jira Admins can create multiple Space scoped rules. Are you a Jira Admin?

If your rule is scoped for only one of the spaces, the item in the other space will not be able to be updated.

Additionally, the Work Item Linked trigger is activated by the creation of the link in the "source" item, which is not necessarily the item where you are initiating the link creation. Work item links are directional. I talked about this directionality and the trigger in my answer to another post:

https://community.atlassian.com/forums/Jira-questions/How-can-I-get-field-from-linked-issue/qaa-p/2807518#M1050229

So even though you are creating the link from the Project A issue, depending on the link relationship you are choosing (A blocks B, or B is blocked by A) the item in Project B may be considered the "source" in the link relationship. If your rule is scoped for only Project A, that would explain why it is not getting triggered.

[Darryl St_ Pierre]

Thanks @Trudy Claspill . Expanding the scope to both spaces allowed the rule to run. It did, however, update the wrong ticket (Project A).

My challenge now is that it seems like I must control what type of link is selected in order for the correct ticket to be updated. I viewed your referenced article and understand the needed conditions; I'm just not sure staff will adhere to a prescribed link type.

[Trudy Claspill]

You may not have to constrain the link.

Can you provide more details about your scenario? i.e.

1. I am viewing an item in Project A. 
2. It doesn't matter what type of item I am viewing
3. From that item I create a link to an item in Project B. 
4. It doesn't matter what type of link I choose.
5. It doesn't matter what type of item I select in Project B.
6. I want to add a specific person (?) as a request participant on the item in Project B.

You did mention that you want to add a Request Participant, which is valid only for Service space types. Can you confirm that Project B is a Service space type?

And is the person you want to add a licensed user of your Jira/JSM instance, or are they a customer?

And does the person already have access to Project B?

[Darryl St_ Pierre]

The scenario:

Team 1 owns Project A and needs to "review" linked items that reside in Project B. 

I'm trying not to give Team 1 agent access to Project B.

Everyone is a customer on Project B.

I know that what I'm doing here will present the agent-view link, which will still be inaccessible, but I'll cross that bridge later.

Both projects are Service Desks. Everyone involved in this scenario is licensed in JSM.

[Trudy Claspill]

Does it matter whether the link is created from Project A to B or from Project B to A?

Does it matter what type of link is selected or the directionality of the link?

Does it matter what type of work items are involved?

If the answers to the above are "No", then you can structure the rule to ensure that the participants are added to the Project B work item in the pair. It might take two rules. Are you interested in that type of solution versus restricting the link types and directionality that can be chosen?