Home → Suggestions →

+1 for Mass Ticket Updates

• Edit

Peeja

01 Dec, 2008 03:55 PM

I know you guys are already working on mass ticket updates, but I want to throw my support behind it. We have an awaiting-deploy tag for tickets which haven't landed on the live site yet. When we deploy, we have to make all of those tickets resolved.

Here's hoping mass updates come soon. :)

1. 1 Posted by Will Duncan on 01 Dec, 2008 04:18 PM

   

   We want to see this feature as badly as you do. I'll check with Rick today and see what our official status is, but I believe the code is in place and just waiting on the UI additions to get hooked up.

   • Edit

2. 2 Posted by Rick on 01 Dec, 2008 11:25 PM

   

   There's only API support. We'll probably throw up a miniapp with an updated API library really soon so people can start playing with it.
   

   I performed a 600 ticket migration on the Datamapper project last week. It went pretty well, but I have some issues to tweak to make the experience better. If you like, I can give you the curl command line arguments.

   • Edit

3. 3 Posted by Peeja on 02 Dec, 2008 03:18 AM

   

   That would be great, thanks! :)

   • Edit

4. 4 Posted by Rick on 09 Dec, 2008 07:13 PM

   

   This will edit every ticket in a ticket bin:

   curl -u TOKEN:x -d "command=state:resolved" http://domain.lighthouseapp.com/projects/1/bins/1/mass_edit.json

   And this will edit every ticket in a ticket query:

   curl -u TOKEN:x -d "query=state:open&command=state:resolved" http://domain.lighthouseapp.com/projects/1/mass_edit.json

   The command takes anything command that you can use when modifying tickets through email or git commits. We'll be expanding that keyword section to its own FAQ entry, with new keywords to use.

   Also, in mass_edits only, you can specify a project or account you wish to move the tickets to:

   curl -u TOKEN:x -d "migration_token=OTHER_ACCOUNT_TOKEN&command=account:foo%20project:bar%20state:resolved" http://domain.lighthouseapp.com/projects/1/bins/1/mass_edit.json

   You need to specify a migration_token that has access to the new or project, unless the first token has access already. We'll be rolling out a brand new api lib really to take advantage of mass_edits, callbacks, and a few other new api options.

   • Edit