Updated Fields when moving a project to a new workflow scheme

So I'm trying to move a large a project to a new workflow scheme but I'm getting this error:

image2016-8-15 15:29:7.png

I don't want to move every open task within that project to one creator? There are over a hundred possibilities. Is it just asking to switch the Creator for tasks with a creator that no longer exists?

1 answer

0 votes

That is not a workflow migration, you are moving issues to a new type. 

Look at the field configuration for the new type, you will find "task creator" is marked as mandatory.  Two simple options:

  1. fill one in during the move, on the screen in your screenshot, maybe using a dummy user
  2. temporarily set the field as optional in the configuration scheme.  The weakness of doing this is that no-one will be able to progress or update the issue without filling it in, but individually, you're more likely to get valid data!

Thanks. I can see that it's mandatory but why can't I just retain the original creator?

It will, where it exists, because you have ticked the "retain" box.  You're getting this because there's at least one issue with a creator that's been deleted, and hence is blank.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

401 views 6 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you