-
Bug
-
Resolution: Low Engagement
-
Low (View bug fix roadmap)
-
None
-
6.4.3
-
None
-
6.04
-
1
-
Severity 3 - Minor
-
Summary
The information at the version panel is not showing
Steps to Reproduce
- Create a new version : eg Version1
- Set the fix version as Version1 & Version2
- Delete Version1
Expected Results
Version2 will have issue = 1 in the version panel
Actual Results
No information is shown
Workaround
Backup prior to performing below
- Run the following SQL
select * from nodeassociation where sink_node_id NOT IN (select id from projectversion); - Delete the node association that does not exist in projectversion
- DELETE from nodeassociation where sink_node_id = XXXXX;
- relates to
-
-
- Closed
-
-
-
- Closed
-
[JSWSERVER-12870] Missing Version information in version panel tab
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
| Labels | Original: affects-server fixme | New: affects-server cleanup-seos-fy25 fixme |
| Minimum Version | New: 6.04 |
| Workflow | Original: JAC Bug Workflow v2 [ 2853212 ] | New: JAC Bug Workflow v3 [ 2934198 ] |
| Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545498 ] | New: JAC Bug Workflow v2 [ 2853212 ] |
| Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1552219 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545498 ] |
| Labels | Original: fixme | New: affects-server fixme |
| Support reference count | New: 1 |
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