Details
-
Suggestion
-
Resolution: Fixed
-
49
-
6
-
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
- relates to
-
JRACLOUD-44163 Record Last Index information (date/time) in JIRA
- Closed