Forums

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

Automation creating a Zephyr issue and setting fields in new issue values

Stephen Johnston
August 28, 2025

I am trying to create automation to create a Zephyr issue from another project. When the automation has created the new issue , I want to set the summary of the new Zephyr issue to use the newly created Zephyr key in the name of the summary i.e 'ZX -12 '

1 answer

Suggest an answer

Log in or Sign up to answer
0 votes
Martin Runge
Community Champion
August 19, 2026

Hi @Stephen Johnston

Have you already found a solution? I guess you are NOT on Zephyr Scale, as its test cases are not Jira issues and live outside the issue store, so they have no Jira key.

The key does not exist until the issue is created, so I would not try to build the summary within the Create issue action. I would set it in a second step, right after creation.

Here is the flow I would give it a try:

  • Keep your Create issue action with any placeholder summary.
  • Add Branch rule / related issues > Most recently created issue.
  • Inside that branch, add Edit issue and set Summary to {{issue.key}} {{issue.summary}}.

Inside the branch {{issue.key}} points to the brand-new issue, so it resolves to your ZX-12 value. If you prefer to stay on the trigger path without a branch, {{createdIssue.key}} also works as a smart value straight after a Create issue action.

Cheers, Martin

 

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
TAGS
AUG Leaders

Atlassian Community Events