nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Automation: Set Fix Version within "Then: Create a New Issue" Failure

Michael Landry_2x1grd

Having this issue where within my Jira Automation where I create a new issue as a result of a label added to a ticket. The new ticket is supposed to have a different fix version, but even though the automation generates the new ticket and the automation log is "Success" --it continues to drop the Fix Version.

The fix version is selected in the gear dropdown of "Choose fields to set"
The fix version exists on tickets created outside the automation.
Labels from the previous ticket are being carried over.
This process has worked for other automations, but for some reason this particular fix version is not working.
The automations act sequentially are setup so that Group or Scrum 1 does their work and adds required labels, generating work for Scrum 2, to Scrum 3, etc. This fix version is the ticket created for Scrum 3 (2 steps down in this workflow)

Any thoughts or suggestions on why this fix version isn't working?

Accepted answers

Valerie Knapp_dpp5c6

Hi @Michael Landry , thanks for your question.

To help with this type of troubleshooting, we typically need more information.

Please can you share

what type of project is this (e.g., company-managed, team-managed, etc.),
an image of your complete automation rule in one image file,
images of any relevant actions / conditions / branches,
an image of the audit log details showing the rule execution, and
explain what is not working as expected and why you believe that to be the case.

Thanks in advance for your collaboration!

All comments

Valerie Knapp_dpp5c6

Hi @Michael Landry , thanks for your question.

To help with this type of troubleshooting, we typically need more information.

Please can you share

what type of project is this (e.g., company-managed, team-managed, etc.),
an image of your complete automation rule in one image file,
images of any relevant actions / conditions / branches,
an image of the audit log details showing the rule execution, and
explain what is not working as expected and why you believe that to be the case.

Thanks in advance for your collaboration!

Bill Sheboy

Updated: removing my list of questions to help focus the discussion.

Valerie Knapp_dpp5c6

Lol @Bill Sheboy , I just copied this from that other post we're working on together. Great minds!

Bill Sheboy

Hi, @Valerie Knapp and that list looks familiar to me ;^)

I will remove my post so we can help focus the conversation.

Kind regards,
Bill

Michael Landry_2x1grd

@Bill Sheboy @Valerie Knapp
Thank you both! To answer questions to the best of my capability:

Team managed
Images attached
Fix Version is not being added in derivative ticket. I am not aware of any particular nuances that is resulting in it not working. This same process (cloned with different labels and fix version) works - so perhaps it is the fix version itself.

Generated Ticket.jpg Audit Log.jpg

Bill Sheboy

Hi @Michael Landry

Thanks for this information, and I just replicated this symptom so this appears to be a defect where:

at this time, the Fix Versions cannot be set from the dropdown field in the Issue Create action, and...
immediately after the issue is created, the Fix Versions cannot be set using the Edit Issue action

I also tested to confirm this was not caused by a version name collision effect.

I hypothesize this is a timing problem related to when the created issue is available to have the Fix Versions (and other fields) set. And I did not find this symptom listed in the public backlog so please work with your Jira Site Admin to submit a defect for it here: https://support.atlassian.com/contact/#/

There is a related defect indicating a possible permissions problem, but that is unlikely based upon the workaround I describe below...

For a workaround, you may used advanced edit with JSON to set the field rather than using the dropdown list: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Fix-Versions

After you remove the field in the Issue Create action, expand the More Options area and enter this expression:

{
  "fields": {
    "fixVersions" : [ { "name": "Content Delivery" } ]
  }
}

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

field

automation

fix-version

jira-automation