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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,480
Community Members
 
Community Events
176
Community Groups

Automation Overriding Original Data

I currently have an automation designed to automatically update two fields, request participants and organization when an issue is created and meets a certain condition.  The rule is currently overriding a value added at the time of creation vs. adding the automated values to the original data.  Is there a way to prevent this?

For examples: Organization ABC is added at time of submission, but based on the rule Organization DEF and GHI should be added.  The desired result is for Organization to contain ABC, DEF and GHI.  What is happening now is ABC is being removed and DEF and GHI are being added.

 

1 answer

0 votes

You will need to change the automation such that it adds options to the field, not just write one.

I ran into this myself, and there's a good answer at https://community.atlassian.com/t5/Jira-questions/Setting-a-multi-select-field-with-Automation/qaq-p/2053912

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS

Atlassian Community Events