Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-13735

Get an internal server error when trying to create an issue with Epic Link via REST API

      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

          Form Name

            [JSWSERVER-13735] Get an internal server error when trying to create an issue with Epic Link via REST API

            Atlassian Update - 10 April 2025

            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

            Aakrity Tibrewal added a comment - Atlassian Update - 10 April 2025 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

            ltyphair added a comment - - edited

            ltyphair added a comment - - edited seems to be fixed by https://jira.atlassian.com/browse/JSW-10333

            You download 6.7.12 manually form the Atlassian Marketplace. HOME-DIR is where your install keeps the jira application data.

            • Stop Jira.
            • Remove the plugin jar file with greenhopper in the name file from <HOME-DIR>/plugins/installed-plugins
            • remove the following directories <HOME-DIR>/plugins/.bundled-plugins and <HOME-DIR>/plugins/.osgi-plugins . They will be regenerated automatically.
            • Copy the jar file for 6.7.12 into <HOME-DIR>/plugins/installed-plugins
            • Start Jira

            I can confirm we did this and it restored the functionality.

            Dale Miller added a comment - You download 6.7.12 manually form the Atlassian Marketplace. HOME-DIR is where your install keeps the jira application data. Stop Jira. Remove the plugin jar file with greenhopper in the name file from <HOME-DIR>/plugins/installed-plugins remove the following directories <HOME-DIR>/plugins/.bundled-plugins and <HOME-DIR>/plugins/.osgi-plugins . They will be regenerated automatically. Copy the jar file for 6.7.12 into <HOME-DIR>/plugins/installed-plugins Start Jira I can confirm we did this and it restored the functionality.

            ltyphair added a comment - - edited

            ltyphair added a comment - - edited seems to be fixed by https://jira.atlassian.com/browse/JSW-10333

            We are seeing this as well. Any ETA on a fix. We are going to have to roll back to 6.7.12 to restore this functionality.

            Dale Miller added a comment - We are seeing this as well. Any ETA on a fix. We are going to have to roll back to 6.7.12 to restore this functionality.

            Alex Bunk added a comment -

            We're experiencing the exact same issue AFTER upgrading to Jira-Agile 6.7.14!

            Alex Bunk added a comment - We're experiencing the exact same issue AFTER upgrading to Jira-Agile 6.7.14!

              Unassigned Unassigned
              yokamoto Yuki Okamoto (Inactive)
              Affected customers:
              15 This affects my team
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: