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

Saving search filters UX discards a user's intended search

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.

      Users accidentally lose their intended searches because they do the following:

      1. User types in a JQL
      2. User clicks "Save" before running the search
      3. JIRA happily saves the search before the user typed in the new JQL.
      4. The UI doesn't prompt the user that the JQL has since changed since the last run. <-- this is the main failure point.

      This problem is a vector for other problems on large JIRA instances (JRA-35627) which causes users to create a filter for every issue in the instance. This can lead to crashes when users use this filter on a:

      • JIRA Agile Scrum board: GHS-12171
      • Or a Two-Dimensional filter against all issues on your system split by assignee/project.

      Try the above two on any instance with a million issues and it'll crash the system.

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

                Created:
                Updated:
                Resolved: