-
Bug
-
Resolution: Low Engagement
-
Low (View bug fix roadmap)
-
None
-
7.4.4
-
7.04
-
1
-
Severity 3 - Minor
-
Summary
Kanban boards will show Done issues if their Fix Version field includes an archived version.
Steps to Reproduce
- Create a new Kanban project with project key KAN
- Create a story, KAN-1.
- Create a version called test-version.
- Edit KAN-1 and set its Fix Version field to test-version.
- Archive the version test-version.
- Move the story to the Done column in the board.
- Click Release and fill the field Version name with the value 1.0.
Expected Results
The issue KAN-1 is no longer shown in the board.
Actual Results
Issue KAN-1 will be displayed on the board under the Done column.
Workaround
- Review the issues still being displayed in the Done column and take note of their values of Fix Version.
- Navigate to the board's Releases page and filter by Archived.
- For every archived version retrieved from step 1, do the following:
- Unarchive the version.
- Releast the version.
- Archive the version back.
- is caused by
-
JRASERVER-10692 Possibility to search issues for NON ARCHIVED or ARCHIVED versions
- Gathering Interest
- is related to
-
JRACLOUD-87026 Issues are not cleared from the Done column in a Kanban board after releasing the version due to belonging to archived versions
-
- Closed
-
Form Name |
---|
[JSWSERVER-16255] Issues are not cleared from the Done column in a Kanban board after releasing the version due to belonging to archived versions
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Labels | Original: pse-request | New: cleanup-seos-fy25 pse-request |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 451970 ] |
Minimum Version | New: 7.04 |
Workflow | Original: JAC Bug Workflow v2 [ 2853229 ] | New: JAC Bug Workflow v3 [ 2938316 ] |
Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2546051 ] | New: JAC Bug Workflow v2 [ 2853229 ] |
Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
Link |
New:
This issue is related to |
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