Problems with using two custom field for Epic Name

[Harold de Bell]

Due to a migration, there are two custom fields being used fro epic name.

In a configuration field I am not able to set one to optional and the other to required. When I change one to optional, this wil last for a short time. There is a process that reverts the optional field into a required field again. I do not know what process causes this and why. Because of this I cannot create Epics, without filling in both custom fields.

I tried a workaround by changing the context from global to the specific projects used by the specific custom fields. For the one that was configured for 177 projects there is als a process that reverts the context to Global again. For the one with 14 projects, the setting didn't change.

It seems that having two custom fields for the epic name are not allowed.

Has anyone experienced the same problem and knows the solution for this?

[Trudy Claspill]

Hello @Harold de Bell 

What process was used to migrate the data? That could help us figure out how this happened.

What version of the product are you using?