Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Automating Issue Summary to include Issue Priority Score When the Score is Updated

Hello,

I'm attempted to create an automation rule that will add the Priority Score to the front of the Issues Summary when the Priority score is changed. I've been able to get the score to add to the front of the summary while keeping the original summary, however the previous score value remains (77.0 77.0 67.0 test bug). I haven't been able to figure out how to remove the previous score value, or how to store the original summary in a custom variable to keep it seperate.

 

 

 

Thanks in advance for you help.

1 answer

Hi @Kyle Bucher -- Welcome to the Atlassian Community!

There are several ways I can think of to solve this use case...varying in degree of effort/complexity:

  1. Add a delimiter after the priority score (e.g. a semicolon) and use the substringAfter() function to grab the rest of summary when updating: {{issue.priorityScore}};{{issue.summary.substringAfter(";")}}
  2. Use the replaceAll() function with a regular expression to remove the priority score.  
  3. Store the summary in a separate custom field and replace summary each time by concatenating the priority score and custom field with summary.  This one seems like a bad idea due to duplicating the summary field data and potentially having it get out sync...and thus requiring an additional rule to resync...and possibly creating a loop... Like I noted, probably not a good solution approach.

Best regards,

Bill

@Bill Sheboy 

Thank you for your assistance, I was able to figure it out but forgot to respond to thank you. The first solution worked like a charm. 

Regards,

Kyle

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

☕️ Monday coffee with Jexo: Weekly Atlassian news roundup | 21st June 2021

Hi community 👋, as every Monday we're bringing you a quick update on what happened in the Atlassian ecosystem last week. There were a few interesting events like for example the announcement of th...

59 views 0 6
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