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,555,975
Community Members
 
Community Events
184
Community Groups

Remembering original associate

Hi,

 

We have In Progress and In Review columns in project. Developer is moving tickete from In Progress to In Review. I want to store current assignee as issue property and then when ticket is rejected In Review - when moving back, automatically assign it to original assignee.

I've created rule that stores current assignee "{{issue.assignee.accountId}}" in "developerAccountId" when moving to "In Review"

And another rule when moving back to assign issue to "Smart value" with value "{{issue.properties.developerAccountId}}"

But that throws an error

" (Specified user does not exist or you do not have required permissions)"

 

Can you help me?

2 answers

Can you explain why it should work? I'm setting {{developerAccountId}} property and in logs when I print out {{issue.properties.developerAccountId}} it prints out correct value. Just assigning doesn't work.

Tom Williams
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 14, 2020

Sounds like a permission issue then. 

Under Rule Details Who do you have as the Actor is it "Automation for Jira"? Try setting this to a user you know has the required permissions. 

I tried that already - but didn't help. Also - I have rules to assign to specific people (i.e. when moving to "QA" column) and that works.

Tom Williams
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 14, 2020

Typo on the Action Smart Value?

{{developer.AccountId}} including the "."

Here's where I'm setting this property and then where I'm trying to use this. I don't think it's the typo because I can print out this value and it looks ok.

 

Screenshot 2020-10-14 at 16.56.31.pngScreenshot 2020-10-14 at 16.58.47.png

Tom Williams
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 14, 2020

Ah, sorry I hadn't realised you were setting this data as an entity. We have a similar use case but we capture the assignee in a custom field called "Developer" so others can see who had developed the Story in the future. 

Your issue is a simple fix :) 

In the Set entity property - Entity type - you currently have "Issue" set should be "User".  

But I want this property to be set on Issue not User. 

0 votes
Tom Williams
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 14, 2020

Hey @Krzysztof Adamski 

This should work for you. 

{{developer.accountId}} 

OR 

if it is a custom field {{customfield_XXXXX.accountId}}

Reassign Rule.png

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events