-
Bug
-
Resolution: Low Engagement
-
Medium (View bug fix roadmap)
-
None
-
6.7.14
-
6.07
-
4
-
Severity 2 - Major
-
1
-
Summary
The totally same symptom as JSW-13407 can be seen on JIRA Agile 6.7.14 but I'm not sure I could reopen the ticket so I create this ticket.
This problem never happened on JIRA Agile 6.7.12.
JSW-13407 has already been fixed. However, JIRA Agile 6.7.14 was released AFTER the fixed version (JIRA Software 7.1.4) had been released.
Environment
- JIRA Agile 6.7.14 (JIRA 6.4.x)
Steps to Reproduce
Please see the description in JSW-13407.
Expected Results
Please see the description in JSW-13407.
Actual Results
Please see the description in JSW-13407.
Notes
Please see my internal comment.
Workaround
Update the Epic Link Field after the ticket has been created. This can be done via REST API
- duplicates
-
JSWSERVER-14623 Creating issue with epic link field through REST causes 500 Internal Error
-
- Closed
-
- relates to
-
PS-5851 You do not have permission to view this issue
[JSWSERVER-13735] Get an internal server error when trying to create an issue with Epic Link via REST API
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Labels | Original: affects-server fixme pse-request warranty | New: affects-server cleanup-seos-fy25 fixme pse-request warranty |
UIS | Original: 2 | New: 1 |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
UIS | Original: 5 | New: 2 |
UIS | Original: 2 | New: 5 |
UIS | Original: 0 | New: 2 |
UIS | Original: 2 | New: 0 |
Minimum Version | New: 6.07 |
Workflow | Original: JAC Bug Workflow v2 [ 2852118 ] | New: JAC Bug Workflow v3 [ 2938075 ] |