-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Currently a custom field's UI lifecycle cannot be controlled properly by a plugin. Since JIRA 6.3.4, each time the issue type or project is changed in the Quick Create Dialog, all custom fields are reset to their default value. This is not always the desired behaviour, specially for custom fields provided by third party plugins like JIRA Agile.
JAG has a sprint and epic picker which should not be reset when creating multiple issues or when an issue type or project is changed.
- relates to
-
JRASERVER-30942 Custom field context default value not updated in Create Issue Screen when changing Projects/Issue Type field
- Closed
-
JRACLOUD-65640 Create another issue doesn't preserve the previous Sprint selected
- Closed
-
JRACLOUD-39498 Custom field UI lifecycle management by 3rd party plugins
- Closed