[#JRA-5447] Release notes included issues that have not been fixed.

JIRA

Release notes included issues that have not been fixed.

Created: 07/Dec/04 09:55 AM Updated: 30/Jul/06 07:35 PM

Component/s:

Reports

Affects Version/s:

3.0.1

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

~~JRA-10404~~ Make 'views' of content (single issue and search request) pluggable, and rewrite default implementations in velocity

Participants:	Ben Hodgkinson, Dmitry Tsitelov, Frank Schimmel, Jeff Turner [Atlassian], Mark Chaimungkalanont [Atlassian], Mark Woon and Scott Farquhar [Atlassian]
Since last comment:	104 weeks ago
Labels:

Description

« Hide

USE CASE:
Release a version.
There are issues with "Fix version/s" is equal to this version and that have as resolution a "Won't Fix" or "Cannot Fix" or any other resolution that fixed.

EXPECTED:
Only issues with status == "Resolved" and resolution == "Fixed" are listed in the release notes.

REAL:
All issues with status == "Resolved" are listed, even those that are "Won't fix" or similar.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] - 07/Dec/04 05:44 PM

Frank,

You've got a point here. However, considering that users / admin can add their own custom resolutions, I wonder what would need to be the logic here? Say if I added a new resolution "Rejected", how would the system know not to include this one?

Perhaps the solution would be to add an additional property for resolutions as a "add to release notes" flag or some such...

Thanks for the heads up!

Cheers

Mark C

[ Permlink | « Hide ]

Mark Woon - 14/Apr/05 03:29 PM

I'm also having prolems with seeing things that weren't fixed on the release notes.

In response to Mark C's comment, how about being able to specify a search to determine which issues would show up in the release notes? I wouldn't want to have to go and identify each issue that should show up.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 19/Apr/05 01:59 AM

Allowing a named filter to determine the release notes contents is a good idea. There already is a filter, but it is hardcoded in ReleaseNoteManager.getIssues()

[ Permlink | « Hide ]

Ben Hodgkinson - 14/Mar/06 07:36 AM

I have exactly the same problem.. on 3.4.2 .. We close an issue as a duplicate and it get's included in the release notes. We don't want those issues listed in the notes.

[ Permlink | « Hide ]

Dmitry Tsitelov - 27/Apr/06 04:16 AM

What I can't understand in this situation is why "not-fixed" resolved issues shall have a non empty "Fix version/s" field?

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 27/Apr/06 08:28 PM

That's a good point. Generally when resolving an issue as eg. "duplicate" we unset the fix-for version.

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] - 22/Jul/06 01:34 AM

This may be tangentally related to ~~JRA-10404~~