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

JQL key,issuekey searches should find moved issues

XMLWordPrintable

    • 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.

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

      Searches should return an issue if the item was moved.

      Example: key = TEST-150

      You've already implemented this in the REST API: JRA-26806 and for the sake of consistency, it would be nice to have it here as well.

      It would also benefit the Confluence JIRA Issue Macro since the

      {jira:key}

      macro doesn't render at the moment if issue is moved.

            [JRASERVER-30074] JQL key,issuekey searches should find moved issues

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3043095 ] New: JAC Suggestion Workflow 3 [ 3671159 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2603028 ] New: JAC Suggestion Workflow [ 3043095 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2552006 ] New: Confluence Workflow - Public Facing v4 [ 2603028 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2343074 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2552006 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2116880 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2343074 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2077035 ] New: JIRA Bug Workflow w Kanban v6 [ 2116880 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 886265 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2077035 ]
            jonah (Inactive) made changes -
            Description Original: Searches should return an issue if the item was moved.

            Example: {{key = TEST-150}}

            You've already implemented this in the REST API: [JRA-26806] and for the sake of consistency, it would be nice to have it here as well.

            It would also benefit the Confluence JIRA Issue Macro since the {jira:key} macro doesn't render at the moment if issue is moved.
            		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-30074].
              {panel}

            Searches should return an issue if the item was moved.

            Example: {{key = TEST-150}}

            You've already implemented this in the REST API: [JRA-26806] and for the sake of consistency, it would be nice to have it here as well.

            It would also benefit the Confluence JIRA Issue Macro since the {jira:key} macro doesn't render at the moment if issue is moved.
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-30074 [ JRACLOUD-30074 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: ho-jql-backend New: affects-server ho-jql-backend

              Unassigned Unassigned
              a38518e05741 David Yu
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: