Allow movement of tickets between projects

324
Feature
Jack
3.1
-
Tickets
Completed
Normal
Normal
4 years ago
3 years ago
0

Description

What does this feature do?

On sites where there are many similarly-related projects, but large enough in scope as not to make sense to be "components" of a larger project, users may sometimes create a ticket under an incorrect project.

As all tickets are stored in a single table, allowing the Manager of Project A to move a ticket to related Project B would be a nice new feature.

What makes this feature interesting?

Unless I am missing something, nothing like this currently exists.

In the case where incorrectly placed tickets are generated, we are currently closing them as invalid placement and opening a new ticket under the appropriate project.

Removing this step by adding the feature described above would help to improve the ticket management process.

Ticket History

4 years and 8 months ago by Jack

  • Changed Milestone from 3.0.7 to 3.1
  • Changed Status from New to Accepted

4 years and 8 months ago by Jack

  • Changed Status from Accepted to Started
  • Assigned ticket to Jack

Moving a ticket will display a "migration" form, this form will allow the user to select new properties for the ticket that aren't shared across projects:

  • Assigned to
  • Component
  • Milestone
  • Version

4 years and 7 months ago by Jack

Almost finished, all that's left to do is use the next ticket id for the new project and add a timeline event for each project.

4 years and 7 months ago by Jack

  • Closed ticket as Completed