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

Record Last Index information (date/time) in Jira Audit log

    XMLWordPrintable

Details

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

    Description

      Problem Definition

      The Indexes page only tells the Jira Administrator if there is a background/foreground re-indexing running at the time. No other details such as when or who trigger the previous re-indexing is stored anywhere.

      Suggested Solution

      Include the details of every re-indexing change in the Audit log, including it start and completion

      • Date of the re-indexing triggered
      • Author/User that triggers the re-indexing
      • Category: Re-indexing start/completed
      • Type: Project/Background/Foreground re-indexing
      • Node: (For Data Center) indicate which node triggers the re-indexing

      Why this is important

      • With bug such as JRASERVER-47045, having information of when a re-indexing is start/complete is useful to easily understand the status of the instance/node.
      • Helps understand if a node is running a re-indexing at the time

      Workaround

      • Proceed to JIRA HOME > Cache > Indexes
      • Check when last this folder was modified.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              ijimoh Ismael Olusula Jimoh (Inactive)
              Votes:
              61 Vote for this issue
              Watchers:
              37 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: