Project

General

Profile

Actions

Feature #1701

closed

New Relation for Copying Branch Issues to other Versions

Added by Sebastian Kopf over 15 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
2008-07-28
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

UseCase:
2 Production Branches, 1 Trunk
Customer submits bug for branch one. After analysing it is decided to also fix the bug in branch two and trunk.
So you have to merge or redo the bugfixing in 2 other releases.
That means you need a referenz for planing, development, time booking and testing for the other two releases.
It would be nice to have a copy to diffrent version feature where you could choose the target versions.
But more important there should be a relation wich represents that it was copy from the original in another version not only that it is related. Maybe nice if Bug number stays the same and is identified with issue + Version number


Related issues

Related to Redmine - Feature #4403: Copy with related taskClosed2009-12-152013-04-17

Actions
Related to Redmine - Feature #6899: Add a relation between the original and copied issueClosedJean-Philippe Lang2010-11-15

Actions
Actions #1

Updated by Sebastian Kopf over 15 years ago

forgot something important. The relation is needed for managment purpose to know wich bugs had to be fixed in how many versions.

Actions #2

Updated by Etienne Massip about 13 years ago

  • Category set to Issues
Actions #3

Updated by Sebastian Kopf almost 11 years ago

  • Status changed from New to Resolved

resolved via Feature 6899

Actions #4

Updated by Toshi MARUYAMA almost 11 years ago

  • Status changed from Resolved to Closed

Thank you for your feedback.

Actions

Also available in: Atom PDF