Unable to create automation between 2 projects

[Deept Sarju Dhanani]

I am wanting to create a global automation between 2 projects. When a new Epic or Task is added in Infrastructure projects and enhancements, based on certain conditions i want it to link to a different project as a child. When i type the following JQL to filter, it gives an error when i validate query: Invalid JQL The value 'Infrastructure projects and enhancements ' does not exist for the field 'project'.

JQL

project = "Infrastructure projects and enhancements " AND issuetype in (Epic, Task) AND status = "To do"

After this i want the trigger to be using

then: link work items. It only gives me option to choose a link type and the work item to link to. No where to choose the project i want to link to.

Is there anything i am missing?

[Christos Markoulatos]

Hi @Deept Sarju Dhanani 

The JQL error is about the project name (and status casing).
Your query has a trailing space inside the quotes:

project = "Infrastructure projects and enhancements " AND issuetype in (Epic, Task) AND status = "To do"

use project keys to avoid such issues

As for the second part

A simple pattern that works across projects:

• Trigger: Issue created (Epic/Task)
• Condition: Your field checks
• Action: Lookup issues with JQL that finds the target in the other project (e.g., by component/label/summary pattern).

Project = DEST AND issuetype = "Task" AND "Some Field" = "{{issue.Some Field}}"

• Action: Link work items → choose link type → Issue: {{lookupIssues.first.key}}

Check this Doc:

Automatically Link issues to other issues with Automation for Jira | Automation | Atlassian Support

Hope this helps!!

[Deept Sarju Dhanani]

The first part worked, it was able to filter the items. Thanks!

For the second part, i am choosing the then add action but no where i can choose the link type and issue like in the link provided https://support.atlassian.com/automation/kb/automatically-link-issues-to-other-issues/Or i need to select another option?

[Marc - Devoteam]

Hi @Deept Sarju Dhanani 

Welcome to the community.

As mentioned by @Christos Markoulatos onder the action option, choose the action lookup issues/

[Deept Sarju Dhanani]

Thanks the look up worked!

[Deept Sarju Dhanani]

After I have done the first action which is the look up, it seems to be working. Now with the second action which is the linking, to the destination, seems to be a minor issue. I have a specific column in the destination called Delivery progress where i manually added the epics and tasks.

Delivery Progress: An estimation of delivery work items from Jira such as epics that are linked to the idea. For more details open each idea and the “Delivery” section.

After the branch, i use edit work item, but the field i am trying to link the work item does not come up under choose fields i.e delivery progress.

Is there something i am doing in correct?

[Bill Sheboy]

Hi @Deept Sarju Dhanani -- Welcome to the Atlassian Community!

In addition to the other suggestions offered...

For the rule you show, I strongly recommend not using conditions in the Work Item Created trigger.  There is a known racetrack timing defect with triggers like this where the rule can start before all the data is available to the rule.  The result is incorrect condition results and occasional rule errors.  Atlassian knows about this defect, is working on architectural changes to address it, and there is no timeline for the resolution.

As a mitigation, you may do the following:

• Always add a Re-fetch Work Item Data action immediately after the Work Item Created trigger.  This will slow the rule slightly as it reloads the data before the steps continue.
• Do not use conditions in the trigger.  Instead, add separate conditions after the re-fetch action.
• Regularly read any automation articles posted in the community to learn when the Atlassian team solves this defect

Kind regards,
Bill