########################################################################################## JILS-36: On Versions Pages Seperate Known Issues from Issue list ########################################################################################## Issue Type: New Feature ----------------------------------------------------------------------------------------- Issue Information ==================== Priority: Major Status: Closed Resolution: Done (2018-01-05 08:39:06) Project: Jira Issue Listing Script (JILS) Reported By: btasker Assigned To: btasker Targeted for fix in version: - 0.1 Time Estimate: 38 minutes Time Logged: 22 minutes ----------------------------------------------------------------------------------------- Issue Description ================== Currently, when viewing a Version information page, you're provided with a list of issues that are assigned to that version. But, without going into the issue, there's no way to see whether it's an issue that's simply been marked as affecting that version, or a fix that's in that version (or both...) I think the simplest solution would be to create a second table underneath, which provides a listing of all issues that match the following criteria - Affects the current version - Fix Version is a different version And label it known issues. The existing issue listing table can then be adjusted to only show issues where _Fix Version_ matches the current version. So the top table will be a list of work completed (or to be completed) in that version, the second will be a list of all bugs later found to be in that version and fixed in a later version. ----------------------------------------------------------------------------------------- Issue Relations ================ - is blocked by JILS-33: Issue Listings: DOM ID changes with every view ----------------------------------------------------------------------------------------- Activity ========== ----------------------------------------------------------------------------------------- 2015-09-23 14:25:32 btasker ----------------------------------------------------------------------------------------- This will mean that we're displaying two issue listing tables on the same page, so JILS-33 needs to be resolved first (otherwise both tables will have the same id in the DOM) ----------------------------------------------------------------------------------------- 2015-09-23 14:31:07 btasker ----------------------------------------------------------------------------------------- Have made a change in JILS-33 which should allow us to proceed, but the work in this issue will also be used to test that change (it's a fairly simple change, so there _shouldn't_ be any oddities introduced). ----------------------------------------------------------------------------------------- 2015-09-23 14:31:09 ----------------------------------------------------------------------------------------- btasker changed status from 'Open' to 'In Progress' ----------------------------------------------------------------------------------------- 2015-09-23 14:43:45 btasker ----------------------------------------------------------------------------------------- Commit _726e81d_ implements the basic structure for this issue, but isn't quite the whole package. If we have the following - FOO1 - Affects ver1,ver2. Fix ver2 - FOO2 - Affects ver1. Fix ver2 Then on the ver1 page things will display as expected, FOO1 and FOO2 will both be in the known issues section. On the ver2 page, both FOO1 and FOO2 will also be in the Known issues section, but FOO1 will also be in the issues section. Once resolved, we can say it was fixed in ver2, so we don't really want it appearing in Known Issues as it makes it look like an unfixed bug in that version. Might also want to look at adding a column to the issues table in the Known Issues section so you can see, at a glance, which version it was fixed in. ----------------------------------------------------------------------------------------- 2015-09-23 14:43:49 ----------------------------------------------------------------------------------------- btasker changed status from 'In Progress' to 'Open' ----------------------------------------------------------------------------------------- 2015-09-23 14:44:15 ----------------------------------------------------------------------------------------- btasker changed timespent from '0 minutes' to '12 minutes' ----------------------------------------------------------------------------------------- 2015-09-23 14:50:56 git ----------------------------------------------------------------------------------------- -- BEGIN QUOTE -- Repo: Jira-Issue-Listing Commit: 726e81d45526c205a2a044a4f379058838fb4937 Author: Ben Tasker