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?
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Typo on the Action Smart Value?
{{developer.AccountId}} including the "."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This should work for you.
{{developer.accountId}}
OR
if it is a custom field {{customfield_XXXXX.accountId}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.