Feature #284

Issues fixed in multiple versions

Added by Nick Read almost 11 years ago. Updated over 3 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Resolution:Duplicate

Description

The short version:

It would be great to be able to say that an issue has been fixed in more than one version of the project.


The long version:

The release model on our project is to have three active branches of the code - trunk for unreleased code, the latest
stable release branch, and the stable release branch before that.

We release a new stable branch every six months, but still need to fix high priority issues that arise in older versions.
Given this, we generally do a QA release of the previously released branches every one or two months. These include
any bug fixes that customers can't go without, but do not have the luxury of upgrading their production systems at that
time.

If we identify a bug that affects both trunk and a released stable version, and we decide that it must be fixed for
existing customers, then we fix the bug and mark it in Jira as fixed for both these versions. This means that the issue
would show up on the change log of each version. It also indicates that that testers must test the issue in both versions
of the code.


Related issues

Related to Redmine - Feature #1675: Add 'affected version' as a standard field Closed 2008-07-23
Duplicates Redmine - Patch #219: Issues fixed in multiple versions New

History

#1 Updated by Nick Read over 10 years ago

Patch #10519 has been submitted to implement this functionality:

http://rubyforge.org/tracker/index.php?func=detail&aid=10519x%x%
amp;group_id=1850&atid=7162

#2 Updated by Felix Schäfer over 7 years ago

  • Status changed from New to Closed

Closing this issue in favor of #219.

#3 Updated by Rick Hunnicutt over 7 years ago

Felix,

You've closed this based on #219 but in the last entry, the author states the patch will most likely not merege into the current tree and that was 3 years ago. Is it a valid resolution at this point? It is still needed for sure.

#4 Updated by Alice Etchegaray over 3 years ago

I agree with Rick, the patch isn't adapted for current tree and it's a pity...
Why don't integrate this functionality into the future versions of Redmine ??

#5 Updated by Toshi MARUYAMA over 3 years ago

  • Resolution set to Duplicate

#6 Updated by Toshi MARUYAMA over 3 years ago

  • Related to deleted (Feature #1675: Add 'affected version' as a standard field)

#7 Updated by Toshi MARUYAMA over 3 years ago

  • Related to Feature #1675: Add 'affected version' as a standard field added

Also available in: Atom PDF