Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Using Automation to transition a Zendesk ticket to a Jira ticket under a specific Epic

Scott Schellhardt
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 20, 2022

I am trying to create an automation rule that will run when you create a ticket from Zendesk to Jira to add that ticket to a Support Epic created for my company. I have been using the "Labels" field and using jira_escalated as the defining condition to align the ticket to the epic but its not working. Please help ! Screen shot below:Screen Shot 2022-07-20 at 2.46.02 PM.png

1 answer

0 votes
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 27, 2022

Hello @Scott Schellhardt

Thank you for reaching out.

Checking your automation rule, I confirm that the smart value that you configured to link the Epic issue is not valid. Allow me to explain:

When adding the action to add a new linked issue in an automation rule, you are basically setting two fields: Issue link type and Linked issues. In your automation rule, you are adding a whole string to the field Linked issues using the {{issue-summary}} smart value. As the "Linked issues" field is not a text field as the comment or description fields, the smart value will not work for that field.

The only value that is supported by the "Linked issues" field is the issue key, which has the following format:

"<Project key>-<issue number>"

For example, let's suppose your Support epic's key is "ABC-123". You should add that key directly to the automation rule to properly map the linked issue, as you can check in the screenshot below:

Screen Shot 2022-07-27 at 16.21.17.png

Additionally, you mentioned that you are trying to link them to an Epic issue. Epic issues can be linked using a child-parent relationship, which is different from the same level issue link that you are currently setting with the automation. You can check the difference between both links in the articles below:

Epic link vs issue link

If you are trying to add the parent-child relationship that is used for Epics, you should use the automation rule to edit the Epic link with the Epic key:

Screen Shot 2022-07-27 at 16.32.17.png

Let us know if you have any questions.

Suggest an answer

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

Atlassian Community Events