Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-8512

Improve documentation on the URL to access Crucible after startup

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.

      In section 6 of the upgrade we state:

      After a few moments, in a web browser on the same machine, go to http://localhost:8060/ (or, from another machine, type http://hostname:8060/ , where hostname is the name of the machine where you installed Crucible).

      If a customer has changed the port Crucible is listening on in their config.xml this can cause some confusion, especially since the startup logs also have this path hard-coded instead of reading it from the configuration file: (CRUC-3590: Log the correct hostname when fisheye is starting up (fixed in Crucible N/A)

      We suggest to add an info/warn panel in that section:

      You may have configured Crucible to listen to a port other than the default 8060, for example
      http bind=":80. In this case, please access Crucible on the configured hostname/port

            [CRUC-8512] Improve documentation on the URL to access Crucible after startup

            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
              tathanassiadou Themis
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: