Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-22154

SOAP API does not work for Moved issues

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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 - JRASERVER-17316 Add a method to remote API (SOAP) that looks up an issue by its key even if the issue has been moved

          • Closed
          relates to

          Suggestion - JRACLOUD-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: