You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I have a simple rule in the next gen service desk - when i assign a user the status will transition. I have 3 users with 3 corresponding transition status
They align with the workflow order - but the names and status get mixed up for 2 of them
I thought it might be to do with permissions - they are all agents but maybe they have to be set up to: https://support.atlassian.com/jira-software-cloud/docs/transition-an-issue-with-automation/ talks of rule actors need correct permissions?
Are you able to shed a bit of light on this problem
Thanks
Hi @Jenny Thompson I am not sure if I understand the issue but on the first look I think your automation is not configured correctly.
Your condition (is assigned to) is not on the same path as your action. It should be:
But I am not really sure I understand it 🙂
Hi Martyn - thanks for your response. I didnt mention that i intend to have a number of people as potential assignee hence the condition 'is one of' and i would have the value as the list of assignees. What i am trying to do is match any name from the list of assignees to the status 'Specialist Analyst - so - when a person in the list gets assigned a ticket the status will change to Specialist Analyst.
Your reply makes sense if assignee is one specific person only - but i have used condition 'is one of' so it can match to a list of people.
However - the status is not working it will change but to another status which follows the same rule but for a different set of users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jenny Thompson ok, but than you have to configure the transition to be done in the branch where condition is set:
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.
Hi @Jenny Thompson ,
As @Martin Bayer _MoroSystems_ s_r_o__ suggest it is the rule problem. can you please describe your questions more clearly as I am also can't understand it better?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi - hope this is clearer
Here is the rule: Set status on assignee to specialist analyst
is one of (eg the condition)
Cecilia Hedberg; Julia Smith; Magdalena Lis-Podjaska (eg the values that the condition compares to)
4. Then transition the issue to the destination status Specialist Analyst (Change the status field to specialist analyst)
-----------------------------------------
So basically if I add one of the 3 user names in the assignee field then the status field should change to Specialist Analyst.
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.
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.