Estimates and dependencies


#1

Hi, long time fan of RT here, trying to get approval to roll this out to our
various teams.

Two “How do I coerce RT 1.0 into…” questions for you folks:

Would there be a way to track time estimates within a queue? For example, a
ticket comes in, it is estimated at 3 hours work. When all the tickets are
listed in priority, we would like to have a good idea of how many tickets
we’d be able to handle in a day.

What if one ticket depends on another for completion? An example would be a
PC install and a wiring install. The PC can’t go in until the wiring is
done, so we’d like some way of keeping track of that. Merging the tickets
is one option, but then we lose a lot of the statistics we find valuable.
The best I could come up with was to add the dependant person to the admin
of the first ticket’s requestor list, so they’d at least get an email and
can change the properties manually.

Will the answers change if we were talking about RT2?

Thanks,

Sean

Sean Walberg swalberg@hsc.mb.ca
Communications Eng, Comm & Info Svcs
Health Sciences Centre [204-787-1010]


#2

There isn’t really any easy way to do this within RT1, aside from maybe
shunting “30 min:” at the beginning of a subject line.

There isn’t a clean way for doing dependencies in RT1.

And yeah, all this is built in to 2.0. :wink:

    -jOn Tue, Mar 06, 2001 at 04:07:41PM -0600, Sean Walberg wrote:

Hi, long time fan of RT here, trying to get approval to roll this out to our
various teams.

Two “How do I coerce RT 1.0 into…” questions for you folks:

Would there be a way to track time estimates within a queue? For example, a
ticket comes in, it is estimated at 3 hours work. When all the tickets are
listed in priority, we would like to have a good idea of how many tickets
we’d be able to handle in a day.

What if one ticket depends on another for completion? An example would be a
PC install and a wiring install. The PC can’t go in until the wiring is
done, so we’d like some way of keeping track of that. Merging the tickets
is one option, but then we lose a lot of the statistics we find valuable.
The best I could come up with was to add the dependant person to the admin
of the first ticket’s requestor list, so they’d at least get an email and
can change the properties manually.

Will the answers change if we were talking about RT2?

Thanks,

Sean


Sean Walberg swalberg@hsc.mb.ca
Communications Eng, Comm & Info Svcs
Health Sciences Centre [204-787-1010]


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

…realized that the entire structure of the net could be changed to be made
more efficient, elegant, and spontaneously make more money for everyone
involved. It’s a marvelously simple diagram, but this form doesn’t have a way
for me to draw it. It’ll wait. -Adam Hirsch