No edit field in bulk change for custom field.

[ToddManUtah]

I have a field (App Version(s)), that I want to change in bulk changes. I select the list of items I want to change, pick edit and go to the "App Version(s)" field. There's a checkbox there, like the other fields, allowing me to select this field for edit. BUT... there is no edit field to enter the new value. I see the edit box for other fields but all I see for App Version(s) is a description.

If I select the checkbox and continue to the next screen, I get an error saying I need to enter a value. But since there's no edit box to enter that value, I'm stuck.

Anyone have any ideas?

[Trudy Claspill]

Hello @ToddManUtah 

What type of field is the App Version(s) field?

Can you show us the bulk edit screen where the field is selectable?

[ToddManUtah]

It's a select list (multiple choice). I'm attaching a screenshot showing the definition and another screenshot of the bulk change tool. The bulk edit screenshot includes a couple of fields above and below so that's it's clear that there is no edit control to enter a new value.

[Trudy Claspill]

Is the field available on the Edit screen for all the issues that are within the scope of the selection you made for Bulk Change?

[ToddManUtah]

I tried making the set JUST stories and JUST bugs and in both cases, I see the same problem.

[Trudy Claspill]

Is the field available on the Edit screen for those types of issues?

Does your selection of issues include just one project, or only projects where the field is available on the Edit screen?

[ToddManUtah]

It is available and setable in the screens/forms themselves. It's only in one project and used in multiple screens/forms. Available context is global.

Short answer: I can edit the field just fine EXCEPT when I try to change it in bulk.

[Trudy Claspill]

I am stumped. I have not been able to recreate your issue yet, but I am using Jira Cloud rather than Jira Server/Data Center.

If your instance is still covered by a support contract, I suggest raising the issue with your Jira Admins and requesting that they open a support case with Atlassian Support.