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

Automation runs twice, fails first time Edited

I've made an automation to set the Assignee as a Request Participant upon assignment. This is to get around the fact that customers can't see the assignee from their portal but they can see Request Participants. It seems to be working, but every time it runs, it fails with "SOME ERRORS", before it runs again and succeeds.

Custom field 10026 is the Request Participants field.

 

First Audit Log output:

Action details:

Edit issue

Error editing issues ITSM-10339(Specify a valid value for customfield_10026 (customfield_10026))

 

Audit Log output 2 seconds later:

Action details:

Edit issue

Issues edited successfully ITSM-10339

 

And here's my JSON under Additional Fields in the "Edit issue fields" action:

{
"update": {
"customfield_10026": [
{ "add": { "accountId":"{{issue.assignee.accountId}}" } } ]
}
}

 

Any ideas? I don't like turning off error notifications but that's my only option now.

1 answer

1 accepted

0 votes
Answer accepted

Hello @t_s_llc ,

Thanks for reaching out and providing all the details.

I played around with the setting and it looks like the issue is getting unassigned before reassigning to a new user in the background, so I added in an "Issue field condition" to only run the rule if "Assignees is not Empty" and it removes the error, the following screenshot shows the audit log after setting the issue to unassigned to trigger the No actions performed message then back to assigned for the success event:

Screen Shot 2021-05-05 at 11.56.51 AM.png

Regards,
Earl

That seems to work, Earl. Thank you!

Like Earl McCutcheon likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM Trial
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

1,116 views 32 33
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