I want to create an Epic and I got two Epic Name fields:
* Epic Name
* Epic Name [deprecated, this field is no longer being used]
both are required. I removed "Epic Name [deprecated, this field is no longer being used]" from my default screen. But Jira still needs to fill out both fileds. :(
I suggest you look into:
You may need to enter a support ticket for this as (apparently) with GreenHopper version 126.96.36.199 we can no longer delete GreenHopper custom fields (they are managed directly by GreenHopper itself).
Hmm, I see what you mean - GreenHopper created custom fields are all shown as "Locked" in the field configs and also appears they cannot be deleted either. I'm wondering how the second field stuck around after your upgrade - what versions of JIRA and GreenHopper are you running?
I'm using the hosted version of JIRA, which I assume is up-to-date, and I also get this error when I try to create an Epic ("Epic Name [deprecated, this field is no longer being used]: Epic Name [deprecated, this field is no longer being used] is required.").
Under custom fields, I see two fields for Epic Name:
Understandably, I enabled the first one, but it it seems I have to use the "deprecated" one instead. Or both? Makes no sense.
I found a fix that worked for me that seems obvious in retrospect. The problem boils down to the fact that the "deprecated" field is required.
For the Default Screen configuration, I added both fields ("Epic Name" and "Epic Name [deprecated, this field is no longer being used]"). Then I configured the "deprecated" one to be Optional instead of required. Then I went back to the Default Screen configuration and removed the "deprecated" field.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs