-
Bug
-
Resolution: Fixed
-
Medium
-
5.1.5, 5.2, 5.2.1, 5.2.4.1, 6.0, 6.3-OD-3
-
5.01
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
In Create Issue Screen, when we change the Project field to other projects, custom fields like Select List and Text Field do not refresh themselves to reflect the Default value specified in the Custom Field's contexts.
Steps to reproduce:
- Create a Select List type custom field.
- Create two contexts for the custom field, one for Project A and another for Project B.
- In both contexts, create the same list of selectable items, but give them different Default values.
- Associate the custom field to the Create Issue screen.
- Create a new issue. In the Create Issue Screen, change the Projects field to Project A. Observe the custom field's default value. (See BugReport3.jpg)
- Change the Projects field again, this time to Project B. Observe that the custom field value does not change to the default value correctly, and appears as "None". (See BugReport4.jpg)
(Screenshot for the contexts: BugReport5.jpg)
Same thing happens for the Text Field custom field. Except that instead of going to "None", the text field retains the default value of the previous selected project.
Only tested for Select List and Text Field, not tested for other custom fields.
- causes
-
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-39981 Custom fields not pre-populated after creating an issue with the 'create another' option
- Closed
- is duplicated by
-
JRASERVER-38232 Custom field's default value does not get updated if the project is changed at the Create Issue screen
- Closed
-
JRACLOUD-66491 Attachments are deselected when changing issue type
- Closed
-
JRASERVER-27475 Attachments are unchecked in quick-create when you change project or issue type
- Closed
-
JRASERVER-29478 Custom Field default value doesn't change right between projects
- Closed
-
JRASERVER-30966 Radio Button Custom Field with Two Contexts Does not Maintain Default Option Selection in The UI
- Closed
-
JRASERVER-31142 Fields with Contexts do not have their default values set properly on Create form when switching from project to project
- Closed
-
JRASERVER-31192 In the Create Issue dialog, Custom Field default value is not updated when switching projects
- Closed
-
JRASERVER-32280 Default Radio Button value is deselected when switching projects
- Closed
-
JRASERVER-32793 Attachments are deselected in the create issue dialog after changing issue type
- Closed
-
JRASERVER-33081 When switching projects in create issue, field configurations are not disassociating
- Closed
- is related to
-
JRACLOUD-65838 Custom fields not pre-populated after creating an issue with the 'create another' option
- Closed
-
JRASERVER-39498 Custom field UI lifecycle management by 3rd party plugins
- Closed
- relates to
-
JRACLOUD-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
-
JRASERVER-27544 When creating a bug and "create another is checked" the description and time tracking fields are not cleared when creating the bug
- Closed
-
JRASERVER-33652 Attachment files are lost after changing project or issue type on create issue pop-up screen
- Closed
-
JRASERVER-33996 Attachment checkbox state lost after toggling project/issue type
- Closed
-
JRASERVER-39426 Attachments field is cleared out on project/issue type switching
- Closed