Work Item Linking Between Projects

[Luke Jackson]

Hi there,

We have a couple of different projects under one JSM instance, there is a requirement for work items in one project to sometimes be copied and linked to a new item in another project, similar to the below:

User logs request > Agent determines this is for the other project > Sends to other project > Existing item remains in original project > New Item created in other project and linked to original.

I can see this is a feature for "Link Work Item" then "Create Linked Work Item" and I can then select a project and request type to assign it to, it then shows in the work item view but I have a couple of queries around this process.

1. Can this be linked to a Jira Automation? So an agent has a one click button that does the process for them?
2. Does the agent need access to both projects to see details in the linked work item?
3. Can an automation be created to allow a comment to be added to both work items?

[Clara Belin-Brosseau_Elements]

Hi @Luke Jackson

As an alternative to Automation (that can be pretty complex sometimes), I can suggest having a look at our app Elements Copy & Sync. It allows you to clone work items from one project to another and link them together.

The configuration only takes a few minutes and then you won't have to do anything manually. 

You can give it a try on your JSM instance for free here.

[Valerie Knapp]

Hi @Luke Jackson , welcome to the Atlassian Community and thanks for your post.

I like to recommend for automations that people take a look at the Automation Library that is provided by Atlassian to get ideas for how to approach these cases.

For example, I think this could be a good rule to use as a basis https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/9918982/207129029 .

I would recommend, in the beginning, that you don't have this called by a trigger of someone writing a comment because I think there is more risk of extra things getting created when people didn't mean for them to be.

In this rule, it's a manual trigger, so the agent would evaluate the ticket, decide, okay but not for this project, call the rule, which clones the ticket into the other project. Then, the agent can close the original ticket as 'won't do' or something like this. In terms of the agent's ability to see the cloned ticket, you can have a permission setting which would allow for them to be able to see the cloned ticket but if they shouldn't work on it anymore, I don't know that that is necessary. 

Please have a look at the rule and share your thoughts.

Best wishes