Moving an issue between projects, JIRA asks for required field values where the field is not in fact required

Scenario:

You are bulk moving issues from Project A to Project B. JIRA asks you to supply values for field X, but field X is not required. In my particular case, the field is a multi-user picker.

Key fact: my JIRA setup replicates users from Active Directory.

1 answer

1 accepted

The fix was to 1) identify users who had been deactivated in AD and 2) remove those users from field X. It's pretty easy to tell - here's an example with three names:

Field X: Washington, George, tjefferson, Lincoln, Abraham

The fact that tjefferson wasn't expanded to "Jefferson, Thomas" means that Tom was deactivated in AD and thus removed from the Directory. The only thing left is the string "tjefferson" in Field X.

If you remove "tjefferson" from Field X, JIRA stops asking you to fill out "required" field X.

Why JIRA does this is a mystery to me. It's not clear to me why a deactivated user makes JIRA believe that the field is required.

Thanks

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,867 views 12 18
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot