Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-22154

SOAP API does not work for Moved issues

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      When you move an issue on JIRA, the key automatically redirects to the new location. Say
      http://jira.atlassian.com/browse/JRA-123
      was moved to
      http://jira.atlassian.com/browse/GOOGLE-5

      If you try to load the first link, with JRA-123, it will automatically go to GOOGLE-5. However, when using the SOAP API, it no longer works. An error is thrown saying the issue JRA-123 does not exist.

      It would be great to have this feature implemented. Thank you.

      Attachments

        Issue Links

          duplicates

          Suggestion - JRACLOUD-17316 Add a method to remote API (SOAP) that looks up an issue by its key even if the issue has been moved

          • Closed
          is related to

          Suggestion - JRASERVER-22154 SOAP API does not work for Moved issues

          • Closed

          Activity

            People

              Unassigned Unassigned
              e7e365384bba Edmund
              Votes:
              7 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: