[0.11] Ticket - Workflow

[cunger]

Hi,

while I am currently playing around with the Configurable Ticket
Workflow in trac 0.11, two questions came to my mind and I do not seem
to find a documented solution to them.


1 - Is it possible to assign default values to specific stages of a
workflow?

the idea is to define one person who is always responsible for the
processing of the report in a specific stage,
say you have committed your fix into the repository and mark the
report as fixed.
the fact that the report's soultion is set to fixed should propagate
it's status to say 'deployed' and set the owner of the report to the
person responsible for deploying the next version of the product to
QA.

The section of the workflow would look somewhat like this:

deploy = fixed -> deployed
deploy.operations = set_resolution, set_owner_to_('Username')
deploy.permissions = TICKET_MODIFY

Is this possible?



2 - Make specific ticket properties inaccessible for reporters
upon ticket creation the reporter schould only be able to set the
values of a subset of the available fields.

How do I configure this?


cu
christian unger

[Christian Unger]

ok I found the solution to my first question:

deploy = fixed -> deployed
deploy.operations = set_resolution, set_owner

deploy.set_owner = username
deploy.permissions = TICKET_MODIFY

now on to my 2nd, anyone?
:-)

cu
christian unger

[Sean Hussey]

Which version are you in? I can't seem to get blah.set_owner =
username to work. Is username in quotes? Anything special about it?

[Richard Liao]

blah.set_owner = username
where username is a specific name. e.g.
blah.set_owner = hussey

[Eli]

On Friday 02 May 2008 06:44:58 am Christian Unger wrote:
> ok I found the solution to my first question:
>
> deploy = fixed -> deployed
> deploy.operations = set_resolution, set_owner
> deploy.set_owner = username
> deploy.permissions = TICKET_MODIFY
>
>
> now on to my 2nd, anyone?

Look into the SimpleTicketPlugin; that may be what you're looking for.

Eli
------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
retr...@gmail.com `-------------------------------------------------

[Sean Hussey]

Yeah, that's not working for me, but maybe I jumped ahead a few steps
in the conversation. I added this to the standard workflow that comes
with 0.11rc1 by default:

testing = new,accepted,needs_work,reopened -> testing
testing.name = Submit to QA for testing
testing.set_owner = hussey
testing.permissions = TICKET_MODIFY
reject = testing -> needs_work
reject.name = Failed testing, return to developer
pass = testing -> closed
pass.name = Passes Testing
pass.operations = set_resolution
pass.set_resolution = fixed

This doesn't handle everything, but the set_owner piece is what I'm
most interested in. The username in question is a valid user and is
in the session table. We have restrict_owner set to true. The
username shows up in that dropdown when we're assigning tickets.

Anything else I should look at?

Thanks!

Sean

[Eli]

On Wednesday 07 May 2008 07:40:10 am Sean Hussey wrote:
> Yeah, that's not working for me, but maybe I jumped ahead a few steps
> in the conversation. I added this to the standard workflow that comes
> with 0.11rc1 by default:
>
> testing = new,accepted,needs_work,reopened -> testing
> testing.name = Submit to QA for testing
> testing.set_owner = hussey
> testing.permissions = TICKET_MODIFY
> reject = testing -> needs_work
> reject.name = Failed testing, return to developer
> pass = testing -> closed
> pass.name = Passes Testing
> pass.operations = set_resolution
> pass.set_resolution = fixed
>
> This doesn't handle everything, but the set_owner piece is what I'm
> most interested in. The username in question is a valid user and is
> in the session table. We have restrict_owner set to true. The
> username shows up in that dropdown when we're assigning tickets.
>
> Anything else I should look at?

testing.operations = set_owner

[Sean Hussey]

Ahh, I see. Thank you! I understand it now.

Sean

[Christian Unger]

Thanks Eli,

also for the AdvancedWorkflowPlugin.
very much appreciated!

SimpleTicket is 0.10 only, but I use blackmagicplugin now to hide
fields.
it's cool also.

I love this configurable workflow!

btw. is there a way to override the hints 'status will be set to blah.
owner will change to blah'?

cu
christian unger

[Eli]

On Thursday 08 May 2008 04:26:32 pm Christian Unger wrote:
> I love this configurable workflow!

:) Thanks!

> btw. is there a way to override the hints 'status will be set to blah.
> owner will change to blah'?

No, though you can do:
[ticket-workflow]
someaction.name = This takes some action on the ticket

HTH,