-
Bug
-
Resolution: Low Engagement
-
Low (View bug fix roadmap)
-
None
-
7.1.0
-
None
-
7.01
-
3
-
Severity 3 - Minor
-
0
-
Summary
When you try to access an older version report for example https://ATLASSIAN_URL/secure/RapidBoard.jspa?rapidView=219&projectKey=TEST&view=reporting&chart=versionReport&version=23000, it will not load the report for version 23000 but instead the browser will redirect the link to https://ATLASSIAN_URL/secure/RapidBoard.jspa?rapidView=219&projectKey=TEST&view=reporting&chart=versionReport&version=23801 (which is the latest).
Steps to Replicate
- Load an older version report from your browser
Expected Result
The older version report is loaded correctly.
Current Result
The older version is not loaded; instead the URL redirects to the latest version report.
Workaround
The older version reports can be accessed via the version drop down list but cannot be accessed directly from the URL.
Note
This happens in JIRA Agile 7.1.7 but I can't find it at the affects version field.
- relates to
-
-
- Closed
-
-
SW-4028 Failed to load
- was cloned as
-
SW-4057 Failed to load
[JSWSERVER-12888] Reloading an older version report URL redirects the page back to the latest version report
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
| Labels | Original: affects-cloud affects-server fixme warranty | New: affects-cloud affects-server cleanup-seos-fy25 fixme warranty |
| UIS | Original: 1 | New: 0 |
| UIS | New: 1 |
| Minimum Version | New: 7.01 |
| Workflow | Original: JAC Bug Workflow v2 [ 2855708 ] | New: JAC Bug Workflow v3 [ 2937864 ] |
| Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542336 ] | New: JAC Bug Workflow v2 [ 2855708 ] |
| Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550714 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542336 ] |
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center