Updating cloned ticket across projects without global admin access

[Anthony B]

Background:

We have two Jira projects - one a Front Door (Service Desk project type) connected to Jira Service Desk and another which is a Backlog (Software project type) containing Sprints etc. The Front Door is for customers to request and view progress of tickets and the Backlog is used by the BA and development team.

When a ticket is created in the Front Door a clone is created in the Backlog. A link is created between the two tickets using the "duplicates" and "is duplicated by" link types.

I have project admin access to both projects but cannot get global admin access. This cannot be changed and rules out using "Project Automation" rules (as far as I can tell) as they require the scope to be set to both projects which is not possible for our team.

What we're looking to achieve: 

1. When the Status of a ticket is updated in the Front Door or Backlog the linked ticket is updated to the same Status. We have this partially working - when a Backlog ticket is updated the Front Door ticket is auto updated via a "Automation" rule with the "A linked issue is transitioned" WHEN trigger. Is the reverse possible?

2. Similar to the above - when a ticket is updated such as a label or comment being added the same should be added to the linked ticket.

Thanks in advance for any help.

[Ste Wright]

Hi @Anthony Birch 

If you have Automation for Jira - using a global rule is the answer.

Whilst you might be a Jira Admin - could you contact your central team and ask them to create the rule(s) for you?

Ste