Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-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

    • Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • Windows 2003 5.2
    • 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.

      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: