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.
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG