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

      When a JIRA Administrator starts a reindex (e.g. after modifying a custom field searcher) there's no guidance about how long this might make JIRA unavailable to all the other users. A useful piece of information to display would be how long the last complete reindex took, as an estimated duration for the next reindex. This information would reassure administrators that it's ok (or not) to start a reindex.

            [JRASERVER-25368] Provide more information before starting a reindex

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3058542 ] New: JAC Suggestion Workflow 3 [ 3687869 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2614674 ] New: JAC Suggestion Workflow [ 3058542 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2578943 ] New: Confluence Workflow - Public Facing v4 [ 2614674 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2358017 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2578943 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2125408 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2358017 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2087871 ] New: JIRA Bug Workflow w Kanban v6 [ 2125408 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 880988 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2087871 ]
            jonah (Inactive) made changes -
            Description Original: When a JIRA Administrator starts a reindex (e.g. after modifying a custom field searcher) there's no guidance about how long this might make JIRA unavailable to all the other users. A useful piece of information to display would be how long the last complete reindex took, as an estimated duration for the next reindex. This information would reassure administrators that it's ok (or not) to start a reindex. New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-25368].
              {panel}

            When a JIRA Administrator starts a reindex (e.g. after modifying a custom field searcher) there's no guidance about how long this might make JIRA unavailable to all the other users. A useful piece of information to display would be how long the last complete reindex took, as an estimated duration for the next reindex. This information would reassure administrators that it's ok (or not) to start a reindex.
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-25368 [ JRACLOUD-25368 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server

              Unassigned Unassigned
              73d805a2526b MattS
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: