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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • 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

I am unable to move an open issue through my workflow. I keep getting an error of "cannot assign issue to nonexistent user (username redacted). It seems that you have tried to perform an illegal workflow operation. If you think this message is wrong, please contact your Jira administrator."

I am using Jira Core v7.5.1 (I know it's end of life) We have had multiple contract companies do work on our instance of Jira, however none of them have left any continuity. Any help would be appreciated.



4 answers

0 votes

Hi @John Adams 

I would check for the validator in your workflow transition first.


Hi John, user assignment is done by a script?

0 votes
Marianne Miller Community Leader Oct 17, 2019

Have you checked your permissions?  Move issues is a specific permission within the project.

Settings | Project | Permissions | Move Issues

Make sure that you are in one of those permission sets (probably the Group) that has permission to move the issues through this project.move issues.gif

if you're not, first  go to your project

Projects | users and roles | Add user to a role

and add yourself to the appropriate group that has this permission.

Is it a particular step/transition in your workflow that you are getting stopped it? If so, look at the post functions for that transition and see it is trying to assign the issue there.

One thing to watch is "Default Assignee" You can assign an issue to a "default assignee" The default assignee is defined in 1 of 2 place

  1. At a project level under roles
  2. On a per component level, as component lead.

Make sure that the default assignee is still with the company, and is a valid assignee. If not, please change it.

With components. make sure the Lead for each one is a real user, or else make sure the "Default Assignee" for the component is "Project Default"

0 votes
Marianne Miller Community Leader Oct 21, 2019

@John Adams , Curious to know what actually resolved your issues?  Are you able to use the workflow correctly now?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

New Cloud Apps Roundup - Spring 2021

Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...

81 views 1 12
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