Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-12648

Backlog to Continue render with Corrupted Index

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • 1
    • 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.

      Problem Definition

      Backlog/Plan mode did not render any issues and throw 500/400 error due to corrupted index with Epic issue type.

      Index can be corrupted at times and not all Enterprise customers can perform full re-indexing at any time of the day as it could take hours of downtime. While index is known to be corrupted, JIRA Agile should continue presenting/rendering Backlog so users can continue to work.

      Suggested Solution

      Continue to render Backlog with all other issues and pop-up warning of missing issues from matching index and database.

      Workaround

      • Perform single project re-index
      • Perform full re-index

      Additional information

      • Customer on JIRA 6.2.3 and Agile 6.6.0 when hit into the problem
      • Tested locally deleting Epic issue via database on JIRA 6.4.5 and Agile 6.7.11

          Form Name

            [JSWSERVER-12648] Backlog to Continue render with Corrupted Index

            Gosia Kowalska added a comment -
            Atlassian Update – 27 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 27 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management

              Unassigned Unassigned
              znoorsazali Zul NS [Atlassian]
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: