[Rt-devel] POLL Re: RT3.8beta - creating child tickets

[Justin Brodley]

This is actually a pretty common scenario, I can put it technical
context.

I have a ticket to install a new customers website in our group. I go to
the server I'm going to install it on, and realize that I don't have
enough disk space to satisfy the install. I'll than create child ticket
to the infrastructure team requesting they had 20gb of space to that web
server.  



Justin Brodley


-----Original Message-----
From: rt-devel-bounces at lists.bestpractical.com
[mailto:rt-devel-bounces at lists.bestpractical.com] On Behalf Of Jesse
Vincent
Sent: Monday, May 12, 2008 9:15 AM
To: Jason Long
Cc: RT developers
Subject: Re: [Rt-devel] POLL Re: RT3.8beta - creating child tickets



> When I "create a related ticket", I would like it to copy the subject 
> and maybe the watchers and priority from the original ticket, but
pretty 
> much nothing else.

The most common use case we've run into is "user included two issues in
one ticket." 

> Here's my fun example. I'm working on ticket #2- "bake a cake". I 
> determine that I don't have enough flour on hand. I create a "child" 
> ticket #3- "get more flour". The child ticket #3 could be in a
separate 
> queue, assigned to someone else. I, the owner of #2, am the requester
of 
> #3. Someone else can take #3, perform the task, and I'll be notified 
> when it is completed.

Given that I don't think you're using RT for cake processing (though I'd
love to hear about it if you are), what do you have for real-world usage
examples? I'm specifically looking for non-contrived situations to help
inform the design ;)

-j

> 
> Jason
> 

-- 
_______________________________________________
List info:
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel