Mailing List Archive: Trac: Users

Workflow

Index | Next | Previous | View Threaded

Jack.Reeves at i-o

Jan 15, 2007, 10:26 AM

Post #1 of 9 (785 views)
Permalink

Workflow

After much investigation, I have decided that the following are not
stupid questions. So here goes.

My outfit is evaluating Trac - and have been for over a month (we are
currently running 0.10.3). At one point we actually decided to switch to
it from our previous issue tracking system, but got so many complaints
that we switched back. The problem is Workflow. No matter how you slice
and dice ways it could be done, we have a QA function and those people
want tickets marked "fixed" but not "closed" until they have been
"verified". On the other hand, developers basically insist upon marking
a ticket fixed when they are done with it - which closes it. There were
other issues as well, and I admit that part of the problem is that
people had spent several years developing habits around the old system.
Nevertheless, the bottom line has become: "It has to support us pretty
much the same way as the old system, or there is no point."

Lest anyone think I am being too critical, everyone loves the wiki
formatting, and the flexibility of the reporting. Developers are also
psyched about the ability of SVN post commit hooks to auto magically
update the ticket status. So, we are trying to make this work. Since it
is obvious we can not be the first outfit with this type of requirement,
I went searching for a solution. Here is what I think I found out.

It appears that the NewWorkflow proposal would meet our needs just fine.

It appears that OUAT there was a large patch that would add this
capability.
It appears that this patch existed into the 0.10 release cycle, but
never became part of the main branch.
It appears that this patch was merged into 0.11dev.
It appears that the NewWorkflow patch was suppose to be subsumed by the
user configurable workflow capability.
Configurable workflow may be part of 0.11, or maybe not.

If I install 0.11dev, will I have the capabilities described in
NewWorkflow and supposedly provided by the 'patch'?
If not, is there a Workflow plug-in available anywhere?
If not, is it possible to regress to some previous stable version of
Trac to which the sandbox/workflow might be successfully applied?

Is there some form of this question that I am not asking properly?

Thx,
Jack

This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please immediately notify the sender and delete the original.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users-unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

manuzhai at gmail

Jan 15, 2007, 10:57 AM

Post #2 of 9 (756 views)
Permalink

Re: Workflow [In reply to]

On 1/15/07, Jack Reeves <Jack.Reeves [at] i-o> wrote:
> It appears that the NewWorkflow proposal would meet our needs just fine.
> It appears that OUAT there was a large patch that would add this capability.
> It appears that this patch existed into the 0.10 release cycle, but never
> became part of the main branch.
> It appears that this patch was merged into 0.11dev.

This is were you go wrong. There was at one point a workflow branch
that did a lot of what you want. It wasn't merged to trunk just yet
because there were some other changes on trunk that needed to be done
before the merge. Those changes (on trunk) then grew quite widespread,
so that merging the workflow branch really didn't make much sense
anymore.

> It appears that the NewWorkflow patch was suppose to be subsumed by the user
> configurable workflow capability.
> Configurable workflow may be part of 0.11, or maybe not.

I'm not exactly sure about the patch. The configurable part of the
workflow was in the workflow branch, but it's not looking like it will
be a part of 0.11.

> If I install 0.11dev, will I have the capabilities described in NewWorkflow
> and supposedly provided by the 'patch'?

Not currently, no.

> If not, is there a Workflow plug-in available anywhere?
> If not, is it possible to regress to some previous stable version of Trac to
> which the sandbox/workflow might be successfully applied?

You can probably base your Trac off of some version of the workflow
branch. Some key revisions that you probably want to look at:

- r2783, in which a workflow branch was first created
- r3872, at which point the workflow branch was pruned,
- at which point it was recopied from trunk at r3873.

So, you could look at r3781 to see if it's any good.

The workflow stuff should reappear for 0.12, but it's probably at
least several months off.

> Is there some form of this question that I am not asking properly?

Quite the opposite, you did quite well. ;)

Regards,

Manuzhai

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users-unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

fen.labalme at gmail

Jan 16, 2007, 2:31 PM

Post #3 of 9 (759 views)
Permalink

Re: Workflow [In reply to]

What needs to happen to get workflow into 0.11? What is holding it
back? It's crucial for my company, and though I'm not a python
developer, if what you need is warm bodies I can provide one (at least
part time). I've sorta always wanted to learn Python - just never got
around to it...

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users-unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

johnstephi at googlemail

Feb 9, 2007, 7:08 AM

Post #4 of 9 (732 views)
Permalink

Re: Workflow [In reply to]

Just wanted to add this is a biggie for us as well. Don't think it'll
stop us from using the product, but it sure hurts since we have the QA
workflow. (Doesn't everybody? ;-)
epaga

On Jan 16, 11:31 pm, "fen" <fen.laba...@gmail.com> wrote:
> What needs to happen to getworkflowinto 0.11? What is holding it
> back? It's crucial for my company, and though I'm not a python
> developer, if what you need is warm bodies I can provide one (at least
> part time). I've sorta always wanted to learn Python - just never got
> around to it...

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users-unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

katzke at gmail

Feb 10, 2007, 7:49 AM

Post #5 of 9 (722 views)
Permalink

Re: Workflow [In reply to]

I think, looking at http://trac.edgewall.org/ticket/869 that someone
is planning a Sprint at PyCon 2007 to try to get it done. For
reference purposes, the spec is at http://trac.edgewall.org/wiki/
WorkFlow.

I'd love to see it too, because the only reason Trac works as well as
it does for us is that we don't have enough people to truly need a
complex workflow. If we had two or three more people, it'd be a royal
PITA to manage.

-Karl

On Feb 9, 9:08 am, "epaga" <johnste...@googlemail.com> wrote:
> Just wanted to add this is a biggie for us as well. Don't think it'll
> stop us from using the product, but it sure hurts since we have the QA
> workflow. (Doesn't everybody? ;-)
> epaga
>
> On Jan 16, 11:31 pm, "fen" <fen.laba...@gmail.com> wrote:
>
> > What needs to happen to getworkflowinto 0.11? What is holding it
> > back? It's crucial for my company, and though I'm not a python
> > developer, if what you need is warm bodies I can provide one (at least
> > part time). I've sorta always wanted to learn Python - just never got
> > around to it...

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users-unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

gaygilmore at gmail

Feb 10, 2007, 4:31 PM

Post #6 of 9 (729 views)
Permalink

Re: Workflow [In reply to]

FWIW, we're only a dev/design/test group of 4, but we miss this too.
I thought Bugzilla's status set was perfect:
- new
- assigned
- fixed
- verified
- closed

and for testing bug fixes you really need the last 2.

I'm going to be watching for this patch, but thought I would share our
current workaround. We added a custom field for Verification and have
several statuses there. So we can tell if the fix was verified in
testing or in production. It is a pain because when a bug is reopened
you need to remember to reset the verification, but that isn't nearly
as bad as never testing a fix.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users-unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

testmonger at yahoo

Mar 14, 2007, 7:32 PM

Post #7 of 9 (711 views)
Permalink

Re: Workflow [In reply to]

customizable workflows are important for our team. (which is actually
not really very easy to do in bugzilla either.) in addition to what is
described above, we want to use an optional step where a bug is
qualified (reproduced) prior to being assigned to an engineer to
investigate. as well as other alternate paths..

==>fixed etc...
new-->qualified==>assigned--| ==>new (reopened)
etc...
==>rejected--|

==>closed

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To post to this group, send email to trac-users [at] googlegroups
To unsubscribe from this group, send email to trac-users-unsubscribe [at] googlegroups
For more options, visit this group at http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

rjollos at gmail

Jul 23, 2013, 9:16 AM

Post #8 of 9 (74 views)
Permalink

Re: Workflow [In reply to]

On Monday, July 22, 2013 8:08:42 AM UTC-7, Stabilo wrote:

> Hi,
> New here and complete novice.
> I am using an existing Trac installation in my company.
> Is it possible to configure Trac to allow access to the workflow change
> dialog from the default Ticket page. Right now if I want to change the
> status of a ticket, I need to first click on Modify, and then a new page is
> opened and I can modify the status there. But I find it would be
> easier/faster to access the workflow change directly at the "default"
> ticket page, without having to click first on "modify". Is it possible?
> Regards
>

When you click on Modify there isn't a page refresh, rather the section is
just expanded. This seems to be coming up fairly frequently on the list,
and there has been discussion about making the expanded/collapsed state on
page load a user preference.

#9807 has some code samples that you can use to customize your site, so
that the Modify section is expanded when the page loads. See (1) in
particular, but I'd recommend reading through the whole ticket,

(1) http://trac.edgewall.org/ticket/9807#comment:25

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscribe [at] googlegroups
To post to this group, send email to trac-users [at] googlegroups
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/groups/opt_out.

lamnguyenhoang at gmail

Aug 2, 2013, 12:28 AM

Post #9 of 9 (32 views)
Permalink

Re: Workflow [In reply to]

thanks

On Tuesday, July 23, 2013 6:16:57 PM UTC+2, RjOllos wrote:
>
> On Monday, July 22, 2013 8:08:42 AM UTC-7, Stabilo wrote:
>
>> Hi,
>> New here and complete novice.
>> I am using an existing Trac installation in my company.
>> Is it possible to configure Trac to allow access to the workflow change
>> dialog from the default Ticket page. Right now if I want to change the
>> status of a ticket, I need to first click on Modify, and then a new page is
>> opened and I can modify the status there. But I find it would be
>> easier/faster to access the workflow change directly at the "default"
>> ticket page, without having to click first on "modify". Is it possible?
>> Regards
>>
>
> When you click on Modify there isn't a page refresh, rather the section is
> just expanded. This seems to be coming up fairly frequently on the list,
> and there has been discussion about making the expanded/collapsed state on
> page load a user preference.
>
> #9807 has some code samples that you can use to customize your site, so
> that the Modify section is expanded when the page loads. See (1) in
> particular, but I'd recommend reading through the whole ticket,
>
> (1) http://trac.edgewall.org/ticket/9807#comment:25
>

--
You received this message because you are subscribed to the Google Groups "Trac Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscribe [at] googlegroups
To post to this group, send email to trac-users [at] googlegroups
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/groups/opt_out.

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads