Automation: Issue with "Copy Sprint from Trigger issue"

[Martin Ibersperger]

Hi there!

I setup an automation rule which is triggered by "Sprint created" and creates both an Xray "Test Plan" and "Test Execution issue". Also both issues should go to the sprint which triggered the rule. Here the "Create issue" step of that rule:

Rule is triggered successfully and both issues get created but they are NOT assigned to the triggering sprint. Audit log says:

Action details:

Create issue

Unknown fields set during create, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -

Sprint (customfield_10020)

Issues created successfully

ABC-123

Our Jira admin could not find any setting to check or change. Pls. give some hints how to solve that issue.

Thx a lot!

Martin

[Jack Brickey · Accepted solution]

Hi @Martin Ibersperger , is the sprint field part of the create screen? If you manually create an issue, is the sprint field present? As an alternate approach, can you try to set the sprint after the issue is created in your rule? In other words, don't try to set the sprint field in the create action, but rather add a subsequent action to edit the issue just created. You may wish to place a refit data after the create issue just to ensure there's no race condition.

[Martin Ibersperger]

Hi,

no, I cannot see sprint field on the creation screen.

Regarding your 2nd approach:

How to setup a subsequent component that refers to an issue?

Adding an "Edit issue fields" I run into an error:

• The rule has been configured with components that require issues to be provided by the trigger. To run these components you must add a branch for this sprint or JQL. The following components require issues: Edit issue

How to set this up properly?

Thx, 

Martin

[Jack Brickey]

After the Create issue component add a re-fetch Action follow this with a Branch related issue and choose "most recently created issue" in the drop down. Finally within that branch add an Edit issue action and set the sprint.

[Martin Ibersperger]

Thx @Jack Brickey, refetching the issue solved the problem!

[Bill Sheboy]

Hi @Martin Ibersperger -- Welcome to the Atlassian Community!

For your original question, the trigger you used is Sprint Created, and so there are no issues provided to the rule.  When you try to create an issue and reference the "trigger issue", there is none.

Instead, you could assign the created issue to that sprint by typing in the smart value {{sprint.id}} in the Sprint field in the action.  The smart value will appear below the field, and then you may select it for use.

Kind regards,
Bill