IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-30678

JQL search for list of issue keys fails if single issue key missing / changed

      I don't understand why a search in the navigator fails if a single key does not exist (e.g. the issue key changed because the issue was moved to another project).

      First of all, the query is actually just a short version of:

      issuekey = CORE-123 OR issuekey = CORE-5555
      

      Hence it should return CORE-123 even though CORE-5555 does not exist.

      Second, why can't it check it the issuekey changed? We are generating release notes via commit messages and have to translate issue keys that changed all the time and only being able to do so via single issue searches (via quicksearch or REST) is not a solution for us.

      A good solution would be to still execute the search but show the warning messages as well!

      This does not cover the translation of issue keys, but would help us a lot

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Data Center'
            1. Jira Data Center
            2. JRASERVER-30678

            JQL search for list of issue keys fails if single issue key missing / changed

                I don't understand why a search in the navigator fails if a single key does not exist (e.g. the issue key changed because the issue was moved to another project).

                First of all, the query is actually just a short version of:

                issuekey = CORE-123 OR issuekey = CORE-5555
                

                Hence it should return CORE-123 even though CORE-5555 does not exist.

                Second, why can't it check it the issuekey changed? We are generating release notes via commit messages and have to translate issue keys that changed all the time and only being able to do so via single issue searches (via quicksearch or REST) is not a solution for us.

                A good solution would be to still execute the search but show the warning messages as well!

                This does not cover the translation of issue keys, but would help us a lot

                        Unassigned Unassigned
                        4ef8826114c9 Fabian Meier
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            4ef8826114c9 Fabian Meier
                            Affected customers:
                            0 This affects my team
                            Watchers:
                            3 Start watching this issue

                              Created:
                              Updated:
                              Resolved: