tag:help.lighthouseapp.com,2008-09-20:/discussions/suggestions/430-bulk-editing-very-cool-but-a-little-jokingly-sadLighthouse: Discussion 2011-04-07T05:35:26Ztag:help.lighthouseapp.com,2008-09-20:Comment/1482002009-04-29T21:13:55Z2009-04-29T21:13:55ZBulk editing - very cool, but a little (jokingly) sad...<div><p>Greetings,</p>
<p>Actually...this being the 'suggestions' area and all... :)</p>
<p>Could you expose bulk update via the API? I ask because my
approach to ticket triage is based around common tickets that my
users regularly report. The Triage app allows me to create a
'bucket', which is a combination of status, milestone, boilerplate,
and tag (I should add 'assigned to' I suppose), which I can then
apply singly or in groups.</p>
<p>I'm guessing by one of the other posts that you're batching bulk
edits for performance, and if you offered the feature through the
API then I would definitely make Triage use that instead of
applying changes one at a time...</p>
<p>-- Morgan Schweers, Cyber<strong>FOX</strong>!</p></div>Morgan Schweerstag:help.lighthouseapp.com,2008-09-20:Comment/1482002009-04-29T21:15:58Z2009-04-29T21:16:28ZBulk editing - very cool, but a little (jokingly) sad...<div><p>Oh actually, we've had the <a href=
"http://help.lighthouseapp.com/faqs/ticket-workflow/ticket-keyword-updates">
API call</a> available for months (and documented for several
weeks) :) I've cited it several times in various discussions on
here where people have been asking for the feature.</p>
<p>It's not in the ruby Lighthouse API yet just because the call
itself breaks the rails API conventions. It's a rather unique API
call that requires an API token (two for cross-account
migrations).</p>
<p>So, apparently the only thing sad thing is my failure in
communicating some of Lighthouse's backend changes better.</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/1482002009-04-29T21:48:56Z2009-04-29T21:48:56ZBulk editing - very cool, but a little (jokingly) sad...<div><p>Greetings,</p>
<p>No, no! The mock-sadness (wryness?) is that it partially
obsoletes some stuff I've been doing. :) Sorry for the
confusion.</p>
<p>I originally had '(If it's not already; I haven't checked.)'
next to the API note, but then I went and didn't see anything
recent in the Caged/lighthouse-api commits, so I figured I'd
'checked', so I removed it.</p>
<p>I'm reading the that API call page now... I'll work on bringing
that into my Triage tool ASAP...as soon as I can understand how to
submit multiple ticket ids...probably an search command I haven't
used before?</p>
<p>How would I update tickets 1, 2, 3, 4, and 5 to
state:resolved?</p>
<p>I definitely understand
<code>http://YOURACCOUNT.lighthouseapp.com/projects/YOURPROJECT/bulk_edit.json?_token=YOURTOKEN&command=state:resolved&query=</code>
but what goes after <code>query=</code> to update specific ticket
ids? (I suppose I could sniff POST operations on your bulk edit
page and guess that it's probably the same parameters, but asking
is probably better supported... :) )</p>
<p>-- Morgan Schweers</p></div>Morgan Schweerstag:help.lighthouseapp.com,2008-09-20:Comment/1482002009-04-29T22:03:44Z2009-04-29T22:03:44ZBulk editing - very cool, but a little (jokingly) sad...<div><p>Greetings,</p>
<p>Also, is there a command to change the title, or (more
importantly) add a new comment to all the tickets as part of the
bulk operation? I usually try to tell users who are watching a
ticket why I'm making a change to a lot of tickets as a brief
comment.</p>
<p>If not, no prob, I'm just poking at it to see what I can do with
it.</p>
<p>-- Morgan Schweers</p></div>Morgan Schweerstag:help.lighthouseapp.com,2008-09-20:Comment/1482002009-04-29T23:00:52Z2009-04-29T23:00:52ZBulk editing - very cool, but a little (jokingly) sad...<div><p>No confusion. Anything sarcastic or wry doesn't translate too
well to text ;)</p>
<p>Hmm, I don't know if it's possible to target individual ticket
numbers. That's something that was added at the last minute when
the checkboxes were added. I may just deprecate that API call and
add a new one based off the same tickets page.</p>
<p>Bulk edit operations do add a comment, but only a standard 'bulk
edit' comment. I'll see about adding an optional message parameter
to it.</p></div>Rick