Details
-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
None
-
None
Description
1. For fields with options (epic status):
If everything is 1:1 like the original configuration, then lock the field, otherwise don't lock the field
1a. Unless there is all projects/appropriate issues field scheme with ZERO options in there. In that case we will just add the options.
1b. Unless there are no schemes, in which case we introduce our own.
2. For fields without option fix up the contexts then lock the field
3. do NOT fix up field names/descriptions for any of the fields
3a. But fix the searcher.
4. for the Rank field, change managed level to "admin" (field creation) plus a message that the field should normally not be created as GH creates the field
5. The default rank field should be fixed up in context and then locked.
Attachments
Issue Links
- is detailed by
-
JSWSERVER-6152 As a GH developer, I would like for the custom fields that GH creates to appear as "managed" in JIRA's administration interface
- Closed