JILS-36: On Versions Pages Seperate Known Issues from Issue list



Issue Information

Issue Type: New Feature
 
Priority: Major
Status: In Progress

Reported By:
Ben Tasker
Assigned To:
Ben Tasker
Project: Jira Issue Listing Script (JILS)
Resolution: Unresolved
Target version: 0.1,

Created: 2015-09-23 14:19:05
Time Spent Working
Estimated:
 
60 minutes
Remaining:
  
38 minutes
Logged:
  
22 minutes


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 Links

Toggle State Changes

Activity


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)
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).
btasker changed status from 'Open' to 'In Progress'
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.
btasker changed status from 'In Progress' to 'Open'
btasker changed timespent from '0 minutes' to '12 minutes'

Repo: Jira-Issue-Listing
Commit: 726e81d45526c205a2a044a4f379058838fb4937
Author: Ben Tasker <github@<Domain Hidden>>

Date: Wed Sep 23 14:40:08 2015 +0100
Commit Message: Initial implementation for JILS-36



Modified (-)(+)
-------
version-issues.php




Webhook User-Agent

GitHub-Hookshot/c703d31


View Commit

A really messy way around it would be to cycle through the outstanding issues and make sure they don't also have the current version linked as IssueFixVersion, but I'd rather find a cleaner way if possible.
It's not much cleaner, but as a temporary measure it works, commit 11fb8e1 makes sure any issues marked as being fixed in the current version won't be listed in the Known Issues section
btasker changed timespent from '12 minutes' to '22 minutes'
btasker changed status from 'Open' to 'In Progress'
I think it would be helpful to have the Fix version displayed in the issue listing table within Known Issues. Don't have time to work on it right now, but I'll leave this issue open/In Progress until it's done.

Repo: Jira-Issue-Listing
Commit: 11fb8e19f607b394e79a03435d632b17ea14bb53
Author: Ben Tasker <github@<Domain Hidden>>

Date: Wed Sep 23 15:11:01 2015 +0100
Commit Message: Made sure issues being fixed/worked on in current version dont display in known version. See JILS-36



Modified (-)(+)
-------
version-issues.php




Webhook User-Agent

GitHub-Hookshot/e8292bd


View Commit

btasker added '0.1' to Fix Version

Repo: Jira-Issue-Listing
Commit: 2ba4dadbfe7c96e4d88d847b85313cdc0de5ca7c
Author: B Tasker <github@<Domain Hidden>>

Date: Mon Apr 25 04:10:27 2016 +0100
Commit Message: Setting up possible future support for remaining item in JILS-36



Modified (-)(+)
-------
templates/json/issues-table.php
templates/json/version-issues.php




Webhook User-Agent

GitHub-Hookshot/cd33156


View Commit

Work log


Ben Tasker
Permalink
2015-09-23 14:44:14

Time Spent: 12 minutes
Log Entry: Building Initial implementation and testing. Also testing JILS-33

Ben Tasker
Permalink
2015-09-23 15:12:05

Time Spent: 10 minutes
Log Entry: Excluding issues from current version from Known Issues list