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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation rules: edit issue field syntax Edited

I have created an automation rule to edit the 'fix version' field with {{sprint.name}} in the current issue, when the sprint changes.

Unfortunately what it does is 'add' sprint name, rather than wipe the field and replace it with the new name, so that I end up with fix versions called 'sprint1.name'-sprint2.name'-'sprint3.name'-sprint4.name'

Is it possible to specify how the value should be changed? Maybe in more options? screengrab below

Screenshot 2021-06-30 at 16.45.07.png

 

FYI, this was the original thread where I made that change.

1 answer

0 votes
Jack Community Leader Jun 30, 2021 • edited

Have you looked to see if there is a action that would allow you to clear the field first?

maybe something like this? I have not tested this…

{
     "update" : {
           "Sprint" : [{"set": []}]
      }
}

Hi Jack, I do not know where to look for this, or how to add such a step.

FYI when you create the action on the issue, it's written in the field 'this field will be cleared' (see below), so the fix version field on the issue is indeed cleared, but the name itself (i.e. in previous step 'create version') is when the problem happens and names are grouped. I do not know how to condition the creation of a fix version name.

Jack Community Leader Jun 30, 2021

Sorry I thought what you were saying was that when your automation runs it’s adding the new value to the existing values in the field. If that is indeed the case my idea was to create an action before your current action to clear the field then you would edit the field the way you’re doing it currently.

it adds the sprint name to an existing fix version name somewhere, i just have no way of seeing where. it creates these versions, see below

Screenshot 2021-06-30 at 17.30.21.png

Hi @l bascle 

Are your stories in multiple sprints, such as carried over from one to the next?

If so, what you may be seeing is because the sprint field is a list of all sprints an issue has been in.

Best regards,

Bill

Like l bascle likes this
Jack Community Leader Jun 30, 2021

That was my thought as well and why I was suggesting to clear the Sprint field first. No I have no idea if that will work. Too I think clearing the sprint field is not necessarily a great idea.

Given these are two list fields (sprint and fixVersion) I can think of two possible solutions, both with assumptions:

  • With the shown rule, assume there is at least one story with one-and-only-one sprint (the current one), and so add a condition to confirm that before creating the version:  {{issue.sprint.size}} equals 1
  • Re-think the approach, and create the version when the sprint starts, enforcing there is a one-to-one between sprints and versions, and set the fixVersion in the stories of the sprint at that time.  This assumes the version is not needed until sprint start.
Like l bascle likes this

Bill, yes you are totally right. Stories don't get completed in the sprint when they were started (boo!), and get carried over from sprint to sprint, so a story is assigned to multiple sprints.

I am not sure which approach from those you suggested is the best... the easiest?

- I tried to implement the first one, but need to define an 'else'. see belowautomationrules.png

- i am not sure I understand the second option. Are you saying basically not to use any automation?

- isn't there a 3rd option to somehow prevent addition of sprints in the sprint field? That seems to be a default feature of JIRA. I would be happy to have a 121 relationship between issues and sprints tbh, but I imagine it would mess up the reporting and burn down etc...

Hi @l bascle 

Sorry for the delay in responding.  For the second approach I noted above, you could do something like this:

  • trigger: sprint starts
  • action: create version
  • branch: on issues in the sprint
    • action: edit issue to assign the fixVersion to the newly created version

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
Community showcase
Published in Jira

⏰ Day in the life of a Jira Admin!

Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...

700 views 2 21
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you