-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
4
-
Minor
-
Issue Summary
Creating a Component during a Move issue operation causes 500 error
Steps to Reproduce
- As a user with Project admin permissions in source and destination projects
- Noting that You need to be a project administrator to add components
- Create 2 projects "Project A" & "Project B"
- Set Components field as Required for Field config on "Project B"
- Leave Project A with no required fields
- Move issue an issue from Project A to Project B
- This will trigger the option to Add a value to the empty required fields during the move operation
- In the required component field Create a new component by typing in any value that does not already exist as a component
- This will display as "the text you type" (New Component)
- Finalize all other requirements and attempt to move the issue
Expected Results
Issue moved with new Component Added to the project
Actual Results
Oops something went wrong 500 error and issue is not moved, component is not created
Workaround
Create the new component in the destination project prior to moving the issue, and select the component from the dropdown list
- is related to
-
JRACLOUD-66824 Moving an issue with a new component causes 500 error.
-
- Closed
-
-
JRACLOUD-67369 Can not create a new component "On the fly", when moving issue from one project to another
-
- Closed
-
-
JRACLOUD-75421 Adding a new component when moving issue returns a 500 error
-
- Closed
-
-
JRACLOUD-79597 Adding a new component when moving issue returns a 500 error
-
- Closed
-
- has action
-
ISSUE-21034 Loading...