I'm currently setting up a new project in a JIRA environment where also GreenHopper is in use. I set up four field configurations for four new issue types. Now everytime JIRA gets restartet I see that the GreenHopper customfield Epic Name becomes required in those field configurations.
Since we also use exocet-lite for creating linked issues in postfunctions, this is painful due to the fact that creation of those linked issues now fails due to a non mapped required field (Epic Name).
Has anyone an idea why this field becomes required after JIRA restart and what we can do to stop this.
We had initially the problem that Epic Name was required and locked in the field configurations, yes. We unlocked the field as described. The difference is in our case Epic Name was only in context of issue type Epic.
The question is, if we lock Epic Name again (this is what we have not done) will it remain optional in the field configuration after a JIRA restart?
Udo, I must have misunderstood your initial description here. I thought the problem was related to the Epic Name field being required for issue types other than Epic.
It sounds like you are interested in making the Epic Name field as optional. If that is the case, I'm afraid that isn't possible, since it is a Greenhopper managed field. You can read more about that here as well:
We managed to unlock and to set the field optional (as described here). However after every Jira restart the field becomes required again. We also tried to lock the field again after we set it to optional, but same result after restart.
This is what I don't understand.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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