Details
-
Bug
-
Resolution: Fixed
-
Low
-
6.4, 6.4.4, 6.4.5, 6.4.7, 6.4.8, 6.4.9, 6.4.10
-
6.04
-
Description
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
On JIRA 6.4.x
- Setup a context path different than /jira for your JIRA instance;
- On a project's overview, click Releases and select a version, then click Release Notes;
- Notice the URL built uses /jira for its context path, which results either on a blank page or a 404 error;
On JIRA 7.0
- Setup a context path different than /jira for your JIRA instance;
- On a Scrum board, expand the Versions sidebar, then expand one of the versions and click Details;
- Click Release Notes, just below the version's name;
- 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
- has a regression in
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
FUSE-3370 Loading...
- was cloned as
-
-
- Closed
-
-
-
- Closed
-
![[JIRA]](/images/icons/generic_link_16.png "[JIRA]"){kind=icon}
- mentioned in
-