Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Request Tracker: Users

batch (not bulk) updating tickets

 

 

Request Tracker users RSS feed   Index | Next | Previous | View Threaded


anarcat at anarcat

May 8, 2008, 11:08 AM

Post #1 of 2 (59 views)
Permalink
batch (not bulk) updating tickets

Hi,

I guess this is a whishlist request, but I'm writing to see if someone
also had such an issue and found an elegant solution already.

I'm using RT a lot to deal with my numerous tickets and todos. Right
now, for example, I have 28 tickets opened in my own "queue" (tickets
that I own). I use priorities to figure out what I'm going to do next.

(One problem is that since we use escalation, even if I set priorities
properly (which already takes a long time), they all go up to
$maxpriority defined on each queue when the due date comes up. So I want
to set the due date and that problem is solved.)

The fundamental problem is it's really a pain to go through N (where N >
5 generally) and update the due date (or priority...) for *every
ticket*.

I know about bulk update, but it doesn't apply since, in that case, I
want to assign potentially different values to every ticket.

So what I envisonned would be to have search results *editable* as is.
Have an option in the search form that would allow the column chosen in
the search to be edited directly. Here's a mockup of the interface that
could be implemented:

http://anarcat.ath.cx/snaps/rt-batch-edit-mockup.png

(Note that in the mockup, only the priority is editable, but anything
could be editable... I guess it would be a "Format" setting in the
"Display columns" box from the search builder...)

So my question is:

1. has anyone done anything like this?
2. if not, how much time would you think this would take to implement?
3. ... and how would you go around implementing it?

Thank you for any input,

--
La guerre, c'est le massacre d'hommes qui ne se connaissent pas,
au profit d'hommes qui se connaissent mais ne se massacreront pas.
- Paul Valéry
Attachments: signature.asc (0.18 KB)


todd at chaka

May 9, 2008, 9:35 PM

Post #2 of 2 (40 views)
Permalink
Re: batch (not bulk) updating tickets [In reply to]

Asset Tracker has this feature. It could be ported to RT.

On Thu, May 8, 2008 at 2:08 PM, The Anarcat <anarcat[at]anarcat.ath.cx> wrote:

> Hi,
>
> I guess this is a whishlist request, but I'm writing to see if someone
> also had such an issue and found an elegant solution already.
>
> I'm using RT a lot to deal with my numerous tickets and todos. Right
> now, for example, I have 28 tickets opened in my own "queue" (tickets
> that I own). I use priorities to figure out what I'm going to do next.
>
> (One problem is that since we use escalation, even if I set priorities
> properly (which already takes a long time), they all go up to
> $maxpriority defined on each queue when the due date comes up. So I want
> to set the due date and that problem is solved.)
>
> The fundamental problem is it's really a pain to go through N (where N >
> 5 generally) and update the due date (or priority...) for *every
> ticket*.
>
> I know about bulk update, but it doesn't apply since, in that case, I
> want to assign potentially different values to every ticket.
>
> So what I envisonned would be to have search results *editable* as is.
> Have an option in the search form that would allow the column chosen in
> the search to be edited directly. Here's a mockup of the interface that
> could be implemented:
>
> http://anarcat.ath.cx/snaps/rt-batch-edit-mockup.png
>
> (Note that in the mockup, only the priority is editable, but anything
> could be editable... I guess it would be a "Format" setting in the
> "Display columns" box from the search builder...)
>
> So my question is:
>
> 1. has anyone done anything like this?
> 2. if not, how much time would you think this would take to implement?
> 3. ... and how would you go around implementing it?
>
> Thank you for any input,
>
> --
> La guerre, c'est le massacre d'hommes qui ne se connaissent pas,
> au profit d'hommes qui se connaissent mais ne se massacreront pas.
> - Paul Valéry
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFII0GHWGBzs0AjcC8RAkrvAJ0dAqWx4FGNfHvP3BEGo20JblXhYwCcDify
> +5ZtGXEljzBhhlRt6/CCnQE=
> =FU4h
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales[at]bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>

Request Tracker users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact lists@gossamer-threads.com
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.