Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-8544

Unable to create issues in Jira 9 from Fisheye

      Issue Summary

      The 'createmeta' endpoint Crucible uses to create issues in Jira is no longer present in Jira 9

      Steps to Reproduce

      • Link Crucible with Jira 9+.
      • Create a code review and add a comment.
      • Click 'Create issue' from a comment.

      Expected Results

      Crucible is able to create issue in Jira 9 as it does in Jira 8

      Actual Results

      Issues are not created and the following WARN message is shown on the Fisheye/Crucible logs

      2023-07-17 12:20:18,400 WARN  [qtp1414967210-56374 ] com.atlassian.crucible.plugins.ril.service.JiraServiceImpl JiraServiceImpl-doRestCallViaApplink - Failed to execute application link request. Server: https://jira.test.com Method: GET Url: https://jira.test.com/rest/api/2/issue/createmeta
          Response: 404 
          Errors: Errors{errorMessages=[Issue Does Not Exist], errors={}}
      

      Workaround

      none available currently

            [CRUC-8544] Unable to create issues in Jira 9 from Fisheye

            Unfortunately still broken for us if you have Jira projects with limited permission schemes attached. :-\

            The issue description of this ticket is still identical but the cause is different so I've opened ticket CRC-14486 with Atlassian support, hope it reaches you soon.

            Geert Lorang added a comment - Unfortunately still broken for us if you have Jira projects with limited permission schemes attached. :-\ The issue description of this ticket is still identical but the cause is different so I've opened ticket CRC-14486 with Atlassian support, hope it reaches you soon.

            Good news Everyone!

            We are happy to announce that Fisheye/Crucible version 4.8.12 has been released!

            As such this issue has been resolved!

            Nate Hansberry added a comment - Good news Everyone! We are happy to announce that Fisheye/Crucible version 4.8.12 has been released! As such this issue has been resolved!

            Marek Parfianowicz added a comment - - edited

            Hi Geert, we're doing pre-release quality checks currently. We aim for 8 May 2023 for the release day.

            Marek Parfianowicz added a comment - - edited Hi Geert, we're doing pre-release quality checks currently. We aim for 8 May 2023 for the release day.

            Is there any ETA when 4.8.12 will be released ? Thanks!

            Geert Lorang added a comment - Is there any ETA when 4.8.12 will be released ? Thanks!

            Hi Paul! We're finishing implementation of this. It will be included in the next bug-fix release, 4.8.12.

            Marek Parfianowicz added a comment - Hi Paul! We're finishing implementation of this. It will be included in the next bug-fix release, 4.8.12 .

            Paul Smith added a comment -

            Really hoping this can be addressed sooner, rather than later, as it's a very important piece of functionality in our workflow that we have suddenly lost

            Unfortunately it doesn't seem possible to downgrade Jira to an earlier version so we're kind of stuck.  Kind of unpleasant that Jira introduced backward-incompatible REST endpoint changes... the point of providing a versioned REST endpoint like v1, v2, etc. is to avoid that kind of thing.

            Paul Smith added a comment - Really hoping this can be addressed sooner, rather than later, as it's a very important piece of functionality in our workflow that we have suddenly lost Unfortunately it doesn't seem possible to downgrade Jira to an earlier version so we're kind of stuck.  Kind of unpleasant that Jira introduced backward-incompatible REST endpoint changes... the point of providing a versioned REST endpoint like v1, v2, etc. is to avoid that kind of thing.

              32bd4bb1181b Artem Iurkov (Inactive)
              nhansberry Nate Hansberry
              Affected customers:
              2 This affects my team
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: