When using a filter in Jira, you are able to put in any large value for the filter ID and Jira produces an HTTP 200

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 8.13.0, 8.20.0, 9.4.9, 9.11.1
    • Component/s: Navigation - Filters
    • None
    • 8.13
    • 1
    • Severity 3 - Minor
    • 0

      Issue Summary

      This is reproducible on Data Center: Yes

      Steps to Reproduce

      1. Search or used a saved filter in Jira
      2. Change the filter value in the URL to any long number

      Expected Results

      HTTP 500 error or denial of using this long of a number

      Actual Results

      Jira allows this and proceeds with a 200 HTTP response 

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            John Vecchio (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: