Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-22277

Allow valid issues to pass through IssueIdValidator

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Gathering Impact (View Workflow)
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: 4.1.2
    • Fix Version/s: None
    • Component/s: JQL
    • Labels:

      Description

      In our Jira 4.1.2 database there are a few issues that are invalid. (They're victims of Jira 3 Bulk Move bugs like JRA-18453. After a move to another project their security level is still set to the old project and thus invalid. But I'm not filing on that bug as I believe that has been fixed in Jira 4. I'm just stating this as an example of how invalid issues still live in our Jira 4.1.2).

      If a user runs a JQL function that returns JiraDataType.ISSUE and the function's results hit one of these invalid issues, they expect to get all their results. If there was an invalid issue, there should be perhaps a warning message that says, "Issue ACME-8242 is invalid," and the rest of the results are returned. Instead they get 0 results and an error message that says only, "A value provided by the function 'jqlFunction' is invalid for the field 'issue'.

      I refer to this bug in a related JQL Improvement request, JRA-22256.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              adc6ee404f6d Jeff Kirby
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated: