-
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
Form Name |
---|
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center