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

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

    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.

      Situation:
      We write a SOAP client for JIRA in JAVA. The client creates issues in JIRA and keeps issue's key.
      If you login directly to JIRA and move the issue to another project in JIRA (issue's key changes), a call of
      com.atlassian.jira.JiraSoapService.getIssue(jiraSessionToken, issuekey)
      using the original key fails.

      On the other hand:
      Searching for an issue in JIRA via 'QUICK SEARCH' (even searching for a moved issue using its 'old' issue key) works fine and shows the (moved) issue.

      Whish:
      A call of
      com.atlassian.jira.JiraSoapService.getIssue(jiraSessionToken, issuekey)
      should find the issue even if the issue was moved i.e. 'issuekey' is an 'old' one.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              57a54e522789 Roberto Luis Rodriguez Estevez
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: