Details
-
Bug
-
Resolution: Fixed
-
Low
-
None
-
14
-
Severity 3 - Minor
-
Description
Summary
Trying to change the issue type while creating a linked issue will result in the field "flashing" and the value returning to the original one.
Steps to Reproduce
- Open a JSM ticket
- Click on Link issue > Create linked issue.
- On the "create linked issue" screen, change the issue type
Expected Results
The issue type will be successfully changed.
Actual Results
The issue type will be reverted to the original one.
GIF of the error: https://share.getcloudapp.com/Z4u6eGWN
The following error appears on the browser console:
"error": "The request was well-formed but was unable to be followed due to semantic errors."
Notes
- The error doesn't seem to affect all JSM projects.
- The error affects just a few users.
Workaround
- Create a test issue (through the create button) using any issue type (NOT request type). Try creating a linked issue again, this should work.
- Note You will need to re-apply this workaround every time you create an issue with a request type in the issue create dialog. This is due to Jira trying to pre-select an option that does not exist in the create linked issue dialog.
- Additionally, you can create the linked issue using the "wrong" issue type and then move it to the correct one. In this case, the bug will persist.
Workaround video: https://jira.atlassian.com/secure/attachment/402620/linked%20issue%20create%20work%20around.mp4