On Apr 6, 10:11 am, "Chris Nelson" <[email protected]> wrote:
> Kirk Strauser wrote:
> > I'm very much a Trac newbie, so if this is already answered, please
> > feel free to tell me to RTFM (as long as you provide a URL).
>
> > At my office that have a list of steps that have to be completed by
> > different people. For example, adding a new customer might look
> > something like:
>
> > - Bob DBA adds them to the customer database
> > - Next, Julie Webadmin adds them to the website
> > - Next, Joe Postmaster creates an email dropbox for them
> > - Finally, Becky Supervisor tells the customer that they're "live".
>
> > A coworker asked me for help to migrate this from a paper process to
> > something web-based. Does Trac have a plugin that could be made to
> > create a series of dependent bugs like this whenever we create a new
> > customer, hire a new person, or whatever?
>
> For what it's worth, we have the same problem.
Sounds to me like this can be solved a couple different ways. Based
on what you said, this sounds more like a workflow than 4 separate
tasks. Since they appear to be sequential, although maybe steps 2 and
3 can be in parallel there. Here's my take:
1.) multi-step workflow:
a. create a custom "component" called "New Customer" (here I am
assuming you might want to use the system for OTHER things as well,
like customer help tickets)
b. Make DBA Bob the default owner of component "New Customer"
c. Next make custom workflow steps which do the following:
I. Create custom status "reqWebsite" action .set_owner =
juliewebadmin (or whatver the track login is) Transition is form
"new"
II. Create custom status "reqMailbox" action .set_owner =
joemailman Transition if from reqWebsite
III. Create custom status "informCustomer" action .set_owner
=beckyboss ...
IV. Set status to closed after that.
2.) May contain elements of 1.) plus, for "simultaneous" part of the
path:
a. install MasterTickets plugin
b. create new ticket types for each "parallel" branch: MakeMail,
MakeWeb
c. The "new ticket" is the master, goes to dbaguy, he creates the db
entry
d. next step is to create a "blocking" ticket, type MakeMail, and set
to block ticket # whatever the "new ticket" number was
e. "clone" the ticket from d. with the CloneTicket Plugin, chance the
type to MakeWeb, and assign to juliewebadmin
f. wait for the 2 blocking tickets are closed, assign the "new
ticket" to beckyboss to inform customer and close.
There are also the TaskTicket plugin, and TracForms which could be
leveraged as well.
That said, automating this would be helpful. I can see many reasons
to do this aside from your specific case. Sounds like a good plugin
request.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
