We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-8512

Improve documentation on the URL to access Crucible after startup

    • 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

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Crucible'
            1. Crucible
            2. CRUC-8512

            Improve documentation on the URL to access Crucible after startup

              • 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

                        Unassigned Unassigned
                        tathanassiadou Themis
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            tathanassiadou Themis
                            Votes:
                            0 Vote for this issue
                            Watchers:
                            2 Start watching this issue

                              Created:
                              Updated: