[#209] enable moving trackers across projects.

Description

Summary:

Detailed description

I thought this was already filed, but I couldn't find it, so this may be a duplicate :-)

Currently, one can move an issue from one tracker (say bugs) to another tracker (feature requests) within a project. An enhancement that would be very useful would be to extend that ability to move trackers across projects.

For example, if we have an issue discovered on 'project A', but it won't be fixed until 'project B' which is a derivative project, it would be nice to be able to just move that tracker item and preserve the original tracker number.

General Information
Submitted by:
Keith de Solla
Date Submitted: 2010-11-10 15:29
Last Modified by: Nobody
Last Modified: 2017-11-02 20:00
Permalink: https://fusionforge.org/tracker/a_follow.php/209
Actions
Monitor
Votes: 0/1 (0%)
Internal Fields
Data Type: Feature requests
Assigned to: Nobody (None)
State: Open
Priority: 1
Extra Fields
Resolution:
none
Difficulty:
none
Target release:
none
Follow-up tabs
Message  ↓
Date: 2010-11-10 21:21
Sender: Keith de Solla

Thanks, Alain. We'll look at that as a possible solution.

-keith

Date: 2010-11-10 18:43
Sender: Alain Peyrat

The problem with moving issues that that lots of information may be lost as the trackers may not have lots of custom fields in common.

Another approach than the move can be used (and already available).

In project B, create the issue. In project A, you can create a custom field of type 'relation' then use this "relation" to track links between your parent ticket and this one.

The relation type allows navigation between tickets, you can easily navigate from A to B and B to A and you can name your relation.

Please give it a try and tell us here if this solution is acceptable for you.

No attached documents

No related commits.

Field Old Value Date By
priority32018-04-22 09:01
Franck Villaume

No relations found.