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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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 deleted user

Hello,

We set up an automation rule so that when an issue is created we can assign it to one of our agents depending on a field that is indicated by the user. Pretty simple.

After specifying the user and publishing the changes, the user is shown as "(deleted user?)". Note that when we write the users name there isn't any suggestion to select an existing user, just a text box.

How can we fix this so the selected user is actually selected? 

Thanks in advance.

1 answer

1 accepted

1 vote
Answer accepted

I would change the type of the input field. There is a field type User Picker. This ensures that the value is actually a user. 

If you cannot change the field for some reason try the advanced field settings in you automation rule (I guess you are using Automation for Jira) 

Here are some examples of the right JSON: https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/

Scroll down until you see the assignee field examples. 

Maybe I didn't explain this correctly, the user input field is in the automation module, so it's not something we'd be able to change.

I've read other issues like this one and it usually says it's an issue with the permissions of the user that owns the custom automation rule. We've tried changing the owner to the administrator and had the same result.

I think I understand. You do something like this:

1.png

In this case Jira does not suggest a valid user (I would consider this as a bug).

 

But when you use a different rule (edit instead of assign). It works just fine (at least in Jira Server). Take a look:

1.png

It worked by editing the field like you said. 

I had to use the users id because the input didn't provide any suggestions. 

Thanks!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

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...

235 views 1 6
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