Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-12648

Backlog to Continue render with Corrupted Index

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Obsolete
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature 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

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

            Ramona Scripcaru added a comment -

            Hey Zulfadli,

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close this bug as it has not gained traction on jira.atlassian.com and seems to be obsolete. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to contact us at https://support.atlassian.com/contact/ 

            Kind Regards,

            Ramona Scripcaru

            Ramona Scripcaru added a comment - Hey Zulfadli, Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to  prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close this bug as it has not gained traction on jira.atlassian.com and seems to be obsolete. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to contact us at  https://support.atlassian.com/contact/   Kind Regards, Ramona Scripcaru

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

                Created:
                Updated:
                Resolved: