#4339 Move tickets between ticket tools/projects

forge-jan-25
closed
nobody
General
None
2013-01-20
2012-06-08
Chris Tsai
No

It would be useful to be able to move tickets between different ticket instances. Specific use cases for support would be:

1) moving confirmed bug reports to engr for further eval/processing. So we can maintain separate ticket queues without needing to manage duplicate tickets.

2) moving tickets that should have been logged to a project instead.

I think both these cases could be covered by only allowing users with admin(?) permissions on both tickets instances to move tickets between them.

We should also consider auto-forwarding from the old ticket URL and not re-using the ticket number after a ticket has been moved. Let's not do this yet. But we do need to figure out how to clean up old references to the old artifact path (e.g. solr and artifact references)

Another concern is how to handle custom fields/statuses that aren't shared by both tickets instances. We should just drop those fields/values if they can't be converted. But we should put a comment on the ticket about the conversion and include the full URL of the prior ticket and also insert all the fields/values that couldn't be converted.

The ticket artifact should stay the same, so that subscriptions and other stuff are preserved.

Related

Tickets: #4339
Tickets: #5654
Tickets: #5656
Forge: Feature Requests: #16
Forge: Site Support: #1421
Forge: Site Support: #1592
Forge: Site Support: #1804
Forge: Site Support: #1806
Forge: Site Support: #1894
Forge: Site Support: #1922
Forge: Site Support: #2261
Forge: Site Support: #2471
Forge: Site Support: #858

Discussion

1 2 3 > >> (Page 1 of 3)
  • FINA PM
    FINA PM
    2012-10-05

    I will pay 100 USD for this feature and 1 bottle of good wine.

    :-)

     
  • Stefan Pendl
    Stefan Pendl
    2012-10-18

    In the old projects it was simple to move a ticket from one tracker to another, so it would be really great to have at least this feature reimplemented in the new or upgraded projects.

    --
    Stefan

     

  • Anonymous
    2012-12-04

    It would be very helpful to the JMRI project to be able to move tickets from one kind of tracker to another within the project, e.g. from Bug to Feature Request. Users put things where-ever they want, basically, so without the ability to move them the various kinds of trackers are impossible to keep straight.

     
  • Dave Brondsema
    Dave Brondsema
    2012-12-04

    • labels: for-support, p3 --> for-support, p3, migration, feature-parity
     
  • Dave Brondsema
    Dave Brondsema
    2012-12-06

    • labels: for-support, p3, migration, feature-parity --> for-support, p3, migration, feature-parity, 42cc
     
  • Dave Brondsema
    Dave Brondsema
    2012-12-06

    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -6,6 +6,8 @@
    
     I think both these cases could be covered by only allowing users with admin(?) permissions on both tickets instances to move tickets between them.
    
    -We should also consider auto-forwarding from the old ticket URL and not re-using the ticket number after a ticket has been moved.
    +*We should also consider auto-forwarding from the old ticket URL and not re-using the ticket number after a ticket has been moved.*  Let's not do this yet.  But we do need to figure out how to clean up old references to the old artifact path (e.g. solr and artifact references) 
    
    -Another concern is how to handle custom fields/statuses that aren't shared by both tickets instances.
    +*Another concern is how to handle custom fields/statuses that aren't shared by both tickets instances.*  We should just drop those fields/values if they can't be converted.  But we should put a comment on the ticket about the conversion and include the full URL of the prior ticket and also insert all the fields/values that couldn't be converted.
    +
    +The ticket artifact should stay the same, so that subscriptions and other stuff are preserved.
    
     
  • Do you have any tips on how interface for this should look like?

    I think we could place 'move ticket' option on ticket edit page (must be shown only if user has admin permission on current tracker). This will display two dropdowns that let you choose project and tracker mount point for ticket. (With current project/mount point selected by default).
    Dropdowns should contain only projects/mount points for which user has an admin permission.

    And, maybe, we need such an option on the 'bulk edit' page?

    What do you think?

     
    • Dave Brondsema
      Dave Brondsema
      2012-12-07

      Hm, I had been thinking about the edit page also, but now that I'm thinking about it more, that page already has a lot on it. It would also be complex if someone changed ticket fields and selected a new tracker to move it to at the same time. What if it were a new page (with two drop-downs, just like you describe). There could be a "Move" link or icon in the action bar (next to rss, email, and edit links)

      I don't think we need to do a bulk edit now, that can be a separate ticket later if needed. It's a good idea though, probably will do it eventually.

       
1 2 3 > >> (Page 1 of 3)


Anonymous


Cancel   Add attachments