Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-59757

When a user generates a Release Notes from a project, the context path is ignored and automatically change to “/jira” resulting in a blank page

    XMLWordPrintable

Details

    Description

      Hello, I have cloned JRA-43658 since this is still reproducible on 7.0.5, 7.0.9 and 7.0.10.

      Summary

      Regardless of the context path setup for JIRA, accessing the Release Notes link from a version's details page builds a URL with context path /jira, which possibly results in a 404 error.

      Steps to Reproduce

      1. Setup a context path different than /jira for your JIRA instance;
      2. On a Scrum board, expand the Versions sidebar, then expand one of the versions and click Details;
      3. Click Release Notes, just below the version's name;
      4. Notice the URL built uses /jira for its context path, which results either on a blank page or a 404 error;

      Expected Behavior

      The context path should be retrieved from the application's Base URL, and not hard-coded.

      Actual Behavior

      Every time the URL for Release Notes is built, the context path is set to /jira.

      Workaround

      Option 1

      You can manually edit the URL from your web browser, adding the right context path (as shown in screenshot below).

      Option 2

      Add the following script in JIRA's Announcement Banner

      <script type="text/javascript">
jQuery(window).load(function(){
	release_report_notes_link = document.getElementById("release-report-notes-link")
	if (release_report_notes_link != null){
		release_report_notes_link.setAttribute("href",release_report_notes_link.getAttribute("href").replace('/jira', AJS.contextPath()));
	}
});
</script>

      Attachments

        Issue Links

          is a regression of

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-43658 When a user generates a Release Notes from a project, the context path is ignored and automatically change to “/jira” resulting in a blank page

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-59489 When a user generates a Release Notes from a project, the context path is ignored and automatically change to “/jira” resulting in a blank page

          • Low - Low priority issues
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-59470 When a user generates a Release Notes from a project, the context path is ignored and automatically change to “/jira” resulting in a blank page

          • Highest - Our top priority issues
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-59470 When a user generates a Release Notes from a project, the context path is ignored and automatically change to “/jira” resulting in a blank page

          • Highest - Our top priority issues
          • Closed

          Activity

            People

              jsimon@atlassian.com Julia Simon (Inactive)
              kgrier kitkat
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: