#4339 Move tickets between ticket tools/projects

asf_release_1.0.0
closed
nobody
General
Cory Johns
2015-02-21
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: #5656

Discussion


  • Chris Tsai
    2012-09-26

    • labels: for-support --> for-support, p3
     

  • Anonymous
    2012-10-05

    Originally by: fina

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

    :-)

     

  • Anonymous
    2012-10-18

    Originally by: stefanpe

    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

    Originally by: *anonymous

    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.

     
  • Created #237: [#4339] Move tickets between ticket tools/projects (4cp)

     

    Related

    Tickets: #4339

    • status: open --> in-progress
     

  • Anonymous
    2012-12-15

    Originally by: wohler

    Hi Igor, I think this feature should be consistent with the other characteristics of a ticket. Thus, there could be a Move to: pulldown within the Edit function of a ticket.

    My use case will be to move all of the tickets from one tool to another, so adding the functionality to the Bulk Edit page is vital. Thanks!

     
  • 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.

    I think, putting the full URL to a prior ticket would be useless, since we need to preserve an old artifact, all changes should be done in place (basically, to move ticket we need to change it's ticket_num and app_config_id). So, old ticket would be lost.

    If we need to preserve an old ticket, then we need create a new artifact for moved ticket, thus we can't preserve the artifact.

    Am I missing something?

     
  • Dave Brondsema
    Dave Brondsema
    2012-12-17

    You're on the right track. Including the old URL won't be very useful. However, I think the change-comment should include something about the old ticket location (number, tool, project if different)

     
  • Closed #237.

    Created #247: [#4339] QA for #237 (Move tickets between ticket tools/projects) (1cp)

     

    Related

    Tickets: #4339

  • Closed #247.

    allura:42cc_4339

     
    • status: in-progress --> code-review
     
  • Cory Johns
    Cory Johns
    2013-01-07

    • status: code-review --> open
     
  • Cory Johns
    Cory Johns
    2013-01-07

    Our tool names are usually but not always lower-cased, so this is missing trackers when I tested it. When populating the drop-down for trackers to move to, the test should be:

    if ac.tool_name.lower() == 'tickets':
    

    Also, the individual posts on the discussion have both app_id and app_config_id which should be updated to ensure data integrity, even though it doesn't affect the function of the ticket.

     
    • status: open --> in-progress
     
  • Created #248: [#4339] Move tickets improvements (1cp)

     

    Related

    Tickets: #4339

  • Closed #248. All changes in allura:42cc_4339a

     
    • status: in-progress --> code-review
     
  • Dave Brondsema
    Dave Brondsema
    2013-01-16

    • qa: Cory Johns
     
  • Cory Johns
    Cory Johns
    2013-01-20

    • status: code-review --> closed
    • milestone: forge-backlog --> forge-jan-25