-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
When creating issues in JIRA after checking the "Create another" checkbox, the custom fields do not retain their values.
It would be very helpful if the custom fields retained their value.
- is caused by
-
JRASERVER-30942 Custom field context default value not updated in Create Issue Screen when changing Projects/Issue Type field
- Closed
- is duplicated by
-
JRACLOUD-65987 Auto-fill has stopped working when creating multiple issues
- Closed
-
JRASERVER-40622 Custom field values are lost when issue type is changed
- Closed
-
JRASERVER-43582 "Create another" option do not copy Summary and Description
- Closed
-
SW-419 Loading...
- is related to
-
JSWSERVER-11105 Inline creating issues to Sprints fails when additional fields are required
- Closed
-
JSWSERVER-11157 Automatically populate the Sprint field when using the "+ Create issue" link in Plan mode
- Closed
-
JRASERVER-36827 "Create another" checkbox when creating tickets - stop copying over all info to new ticket
- Gathering Interest
- relates to
-
JRACLOUD-65810 Auto-fill has stopped working when creating multiple issues
- Closed
-
JRACLOUD-65987 Auto-fill has stopped working when creating multiple issues
- Closed
-
JRASERVER-40125 This issue is automatically pre-populated with your previous issue details, while leaving the Summary, Description, and Time Tracking fields blank.
- Closed
-
JRACLOUD-39981 Custom fields not pre-populated after creating an issue with the 'create another' option
- Closed
- Testing discovered
-
JRASERVER-41586 Unable to change issue type in Custom mode
- Closed
- is depended on by
-
SW-638 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...