Forums

Articles
Create
cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 

Automation Help: Linking a Created Issue to the Trigger Issue from a Form Submission

Stefan Froehlich
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 14, 2025

Hi everyone,

I'm working on a Jira Service Management automation and running into trouble with linking issues correctly.

šŸŽÆ Goal:

When a form is submitted (not just when an issue is created), I want to:

  1. Check if a checkbox field (application_access) has any values selected.
  2. If so, create a new issue (e.g., a task for IT Operations).
  3. Link that new issue back to the original issue where the form was submitted.

🧪 Current Setup:

  • TriggerForms submitted
  • Form field: application_access (checkbox with options: Application AApplication B)
  • Smart values used:
    • {{forms.last.application_access}} ā€“ works fine in logs
    • {{triggerIssue.key}} ā€“ resolves correctly in logs
    • {{issue.key}} ā€“ also resolves correctly
  • Create Issue: Works fine, issue is created
  • Link Issues: Audit log says it linked, but no link appears in the UI

🧠 What I’ve Tried:

  • Logging {{triggerIssue.key}} and {{issue.key}} ā€“ both resolve to the original issue
  • Using "Trigger work item" in the Link work item action
  • Using ā€œMost recently created work itemā€ in the link work item action
  • Using {{triggerIssue.key}} as the target
  • Manually linking the issues works fine, so the link type is visible

ā“ Question:

How can I reliably link the newly created issue to the issue where the form was submitted? Is there a known issue with linking from a created issue to the trigger issue in this context?

Any help or examples would be greatly appreciated!

Thanks in advance šŸ™
Stefan

 

1 answer

1 accepted

0 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 14, 2025

Hi @Stefan Froehlich 

Without seeing the specifics of your rule and audit log details...

 

First, into which project are you creating the new issue: the same as the trigger issue's form or a different project? 

If you are creating it a different project, the rule will need at least multiple-project scope to add the link after the issue is created.  The reason is single-project scope rules can create / clone issues into other projects but they cannot view or alter them otherwise.

As an alternative, the link may be added when the issue is created (removing the Link Issues action) by selecting the Linked Issues field in the Create Issue action.

 

If that does not help, please post the following to supply more context:

  • an image of your complete automation rule in a single image for continuity
  • images of any relevant actions / conditions / branches
  • an image of the audit log details showing the rule execution

 

Kind regards,
Bill

Stefan Froehlich
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 15, 2025

Hi Bill,
thank you for your response.
Let me start by saying, I ran the automation today again to create a new audit log for this purpose and for whatever reason it just worked now...

However, I am still posting the automation and the audit log from today as well as yesterday's here:

automation.png

The only odd thing about the audit log is why it would show the created work item twice.


audit log.png

The only difference here is that yesterday's audit log shows a checkmark at Link work items but then doesn't show the actual tickets linked

audit log yesterday.png


Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 15, 2025

Thanks for the additional information, and...it is quite curious where without changes it worked this time.

Perhaps this is a timing problem caused by a delay after the create or from the forms submitted trigger.  To help mitigate that cause, after the Create Work Item action please add a Re-fetch Work Item Data action.  That will slow the rule slightly to reload the data before it proceeds.

Stefan Froehlich
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 16, 2025

Thank you Bill! will do that. 

Kind regards,
Stefan

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events