Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bulk Change requiring field change

Kevin Dalton
Contributor
June 23, 2015

We have discovered that when Bulk Changing the Status if there is required field that is already populated the bulk change is requiring it be selected and changed even though all the issues have the field populated.  Is this working correctly or should this field not be required to be changes since all issues have it populated.

1 answer

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 23, 2015

That's correct.  Although the mandatory thing is incidental.

The point of bulk change is that you make the same change to all the issues you have selected.  If you change a field, then the new value is supposed to go on to all the issues selected.

The mandatory flag is just making it a bit difficult for you - it's not historical, it only acts now.  You've got at least one issue that has not had the field set, so JIRA is obeying what you've now told it and requiring a value for it.  That's nothing to do with bulk edit really - it would do the same for each issue if you did them individually, but it is having an impact on what you're trying to do with bulk edit.

Two options:

  • Temporarily make the field optional while you do the edit
  • Split the bulk edit into two, taking the current filter and adding "and <custom field> is empty" for one set and "and <custom field> is NOT empty" for the other.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events