-
Bug
-
Resolution: Cannot Reproduce
-
Low
-
None
-
1
-
Severity 3 - Minor
-
Error 500 appears when issue is moved from one project to another with a new componet.
Recreate:
1. Go to a JIRA ticket
2. In the ... menu, click Move
3. Select a project
4. Click Next
5. Leave the Status selection, and click Next
6. In the Components field, enter a new component name
7. Click Next
8. Click Move
Issue:
A 500 error is thrown.
From JIRA Logs:
2017-05-02 10:35:43 - New log file found at /data/jirastudio/jira/j2ee_jira_86d054a6e27b0bb570db/log/main/current
2017-05-02 10:35:43.047227500 name = tempo-data-exporter,
2017-05-02 10:35:43.047227500 version = 1.0.10,
2017-05-02 10:35:43.047227500 parameters = {
2017-05-02 10:35:43.047228500 plugin-icon = images/tempologo_white_16px.png,
2017-05-02 10:35:43.047228500 plugin-logo = images/tempologo_white_130px.png,
2017-05-02 10:35:43.047228500 },
2017-05-02 10:35:43.047232500 enabled = true,
2017-05-02 10:35:43.047232500 },
2017-05-02 10:35:43.047232500 ],
Expected Results:
The issue should have been moved and the new component should have been created.
Workaround:
To get around this, the user can click the back arrow twice. This will take them back to the component screen. There it can be seen that the component was created, the user can select it again, and then next all the way through and move the issue.
- relates to
-
JRACLOUD-94556 Creating new Component during work item Move operation triggers 500 error
-
- Gathering Impact
-