Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-7342

As a user I want to clear the startup timeout banner without restarting Fisheye

XMLWordPrintable

    • 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

      If there is a timeout detected during startup there will be a banner in the UI mentioning the timeout. As per our resource the only way to clear this banner is to restart the application which will clear the banner if there is not timeout detect during the subsequent startup process: https://confluence.atlassian.com/fishkb/fisheye-timeoutexception-after-20000ms-banner-753436420.html

      Restarting the application may not be possible if a change/maintenance window must be scheduled as per required business processes. This means that the banner will be displayed until the next change/maintenance window which could be days or months.

      Suggested Solution

      • Document either a way to remove the banner without restarting the application or add information to that resource that contains the rationale for not providing such an option.

      Workaround

      • This message is produced by our bundled fecru-healthsource-plugin. As a workaround the plugin can be disabled until the instance can be restarted.

            [FE-7342] As a user I want to clear the startup timeout banner without restarting Fisheye

            Marek Parfianowicz added a comment -
            Atlassian Update – 8 July 2024

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Kind regards
            Marek Parfianowicz
            Principal Engineer

            Marek Parfianowicz added a comment - Atlassian Update – 8 July 2024 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Kind regards Marek Parfianowicz Principal Engineer

              Unassigned Unassigned
              nhansberry Nate Hansberry
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: