Error after renaming a custom field

Question

Hi All,

I am experiencing the following issue - I wanted to replace a custom field with a new one. So what I did is renamed the existing one "XXX" to "OLD". And created new one called "XXX". Then removed "OLD" from all the screens. However, now that I open several screens, it does not let me proceed telling me that "XXX" is required and I need to select a value, although I have selected one. When I add "OLD" back to the screen, the issue disappears.

Any ideas how I can fix this? I read something about re-indexing but I don't seem to have this option in my Advanced Admin settings.

Thank you all in advance!

Nic Brough -Adaptavist- · Answer

Ok, then your workflow has a validator on it that is looking for the obsoleted field, probably finding it by id rather than name.

Lubomira Nikolova · Answer

Hi All,

Neither the old one, nor the new one were configured as mandatory. On other screens, I am able to proceed without entering any values.

Thanks

Martin Bayer _MoroSystems_ s_r_o__ · Answer

@Lubomira Nikolova what about Fields configuration? Is it possible that "OLD" field is marked as mandatory?

https://confluence.atlassian.com/adminjiracloud/issue-field-configurations-844500794.html