Mailing List Archive: Trac: Users

multiple end-states

Index | Next | Previous | View Threaded

joost.t.hart at planet

Oct 22, 2009, 2:03 AM

Post #1 of 7 (530 views)
Permalink

multiple end-states

Hi,

Is there a simple means to tell trac (0.11.5) with a configured ticket work flow that it has multiple end states, e.g. closed and rejected?

This would (need to) redefined 'Active' (as resulting from several implicit queries, e.g. the ones used on the Roadmap page) appropriately.

If this is not possible: Can I change the queries on the Roadmap page (and related) myself (or can I paste the existing stuff in a new wiki that I can edit?)

My final way out would be to use the Resolution attribute to differentiate between various end states, but I do not really like this (did use it to denote the testing result in a Verified state ;-) ).

Thanks,
joost.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Chris.Nelson at sixnet

Oct 23, 2009, 4:52 AM

Post #2 of 7 (498 views)
Permalink

Re: multiple end-states [In reply to]

joost.t.hart [at] planet wrote:
> Is there a simple means to tell trac (0.11.5) with a configured
> ticket work flow that it has multiple end states, e.g. closed and
> rejected?

We considered such a plan and dismissed it. There are just too many
places where Trac and plugins look for "not closed" for that to work
well.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

joost.t.hart at planet

Oct 28, 2009, 10:07 AM

Post #3 of 7 (476 views)
Permalink

Re: multiple end-states [In reply to]

Hi,

Found a solution to the problem I described (rather than the solution I suggested myself :-) .

----------------
/conf/trac.ini:

[milestone-groups]
closed = closed,rejected
closed.order = 0
closed.css_class = closed
closed.label = concluded
closed.overall_completion = true

active = *
active.order = 1
active.css_class = open
active.label = in progress
-----------------

This nicknames closed+rejected tickets as 'concluded' and marked them as completed in the roadmap overview.

Bingo.

Cheers,
joost.

________________________________

Van: trac-users [at] googlegroups namens joost.t.hart [at] planet
Verzonden: do 22-10-2009 11:03
Aan: trac-users [at] googlegroups
Onderwerp: [Trac] multiple end-states

Hi,

Is there a simple means to tell trac (0.11.5) with a configured ticket work flow that it has multiple end states, e.g. closed and rejected?

This would (need to) redefined 'Active' (as resulting from several implicit queries, e.g. the ones used on the Roadmap page) appropriately.

If this is not possible: Can I change the queries on the Roadmap page (and related) myself (or can I paste the existing stuff in a new wiki that I can edit?)

My final way out would be to use the Resolution attribute to differentiate between various end states, but I do not really like this (did use it to denote the testing result in a Verified state ;-) ).

Thanks,
joost.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

cboos at neuf

Oct 28, 2009, 10:17 AM

Post #4 of 7 (476 views)
Permalink

Re: multiple end-states [In reply to]

joost.t.hart [at] planet wrote:
> Hi,
>
> Found a solution to the problem I described (rather than the solution
> I suggested myself :-) .
>
> ----------------
> /conf/trac.ini:
>
> [milestone-groups]
> closed = closed,rejected
> closed.order = 0
> closed.css_class = closed
> closed.label = concluded
> closed.overall_completion = true
>
> active = *
> active.order = 1
> active.css_class = open
> active.label = in progress
> -----------------
>
> This nicknames closed+rejected tickets as 'concluded' and marked them
> as completed in the roadmap overview.
>
> Bingo.
>

Nice ;-)

Any chance you could write a short note about this problem + its
solution in CookBook/Configuration/Workflow (for example)?

-- Christian

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

joost.t.hart at planet

Oct 28, 2009, 11:57 AM

Post #5 of 7 (474 views)
Permalink

Re: multiple end-states [In reply to]

Christian Boos wrote:
> Nice ;-)
>
> Any chance you could write a short note about this problem + its
> solution in CookBook/Configuration/Workflow (for example)?
>
> -- Christian
>

Sure!

But not so sure how to get this started. Since this page does not seem
to exist yet, I guess I have to edit some existing page first, add some
link to the new page over there, and only then (after following this new
link) start editing the new page, right?

The problem is that the only suitable reference to the new page seems to
be a TitleIndex in the cookbook index page. Smells like a chicken/egg
problem :-)

How to proceed?

Cheers,
joost.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

cboos at neuf

Oct 28, 2009, 12:22 PM

Post #6 of 7 (475 views)
Permalink

Re: multiple end-states [In reply to]

Joost 't Hart wrote:
> Christian Boos wrote:
>
>> Nice ;-)
>>
>> Any chance you could write a short note about this problem + its
>> solution in CookBook/Configuration/Workflow (for example)?
>>
>> -- Christian
>>
>>
>
> Sure!
>
> But not so sure how to get this started. Since this page does not seem
> to exist yet, I guess I have to edit some existing page first, add some
> link to the new page over there, and only then (after following this new
> link) start editing the new page, right?
>

Not necessarily. Just follow:
http://trac.edgewall.org/wiki/CookBook/Configuration/Workflow
and create the page.
Typing a page name in the quick search box also works.

As you've found out...
> The problem is that the only suitable reference to the new page seems to
> be a TitleIndex in the cookbook index page.
... it will then get referenced automatically from the CookBook page.

There are not that many pages yet in this hierarchy, but as the content
eventually grows, we could link only the top categories pages there
(Installation, Configuration, ...) and in those, the more detailed content.

-- Christian

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

joost.t.hart at planet

Oct 28, 2009, 4:06 PM

Post #7 of 7 (477 views)
Permalink

Re: multiple end-states [In reply to]

Christian Boos wrote:
> Joost 't Hart wrote:
>
>> Christian Boos wrote:
>>
>>
>>> Nice ;-)
>>>
>>> Any chance you could write a short note about this problem + its
>>> solution in CookBook/Configuration/Workflow (for example)?
>>>
>>> -- Christian
>>>
>>>
>>>
>> Sure!
>>
>> But not so sure how to get this started. Since this page does not seem
>> to exist yet, I guess I have to edit some existing page first, add some
>> link to the new page over there, and only then (after following this new
>> link) start editing the new page, right?
>>
>>
>
> Not necessarily. Just follow:
> http://trac.edgewall.org/wiki/CookBook/Configuration/Workflow
> and create the page.
> Typing a page name in the quick search box also works.
>
> As you've found out...
>
>> The problem is that the only suitable reference to the new page seems to
>> be a TitleIndex in the cookbook index page.
>>
> ... it will then get referenced automatically from the CookBook page.
>
> There are not that many pages yet in this hierarchy, but as the content
> eventually grows, we could link only the top categories pages there
> (Installation, Configuration, ...) and in those, the more detailed content.
>
>
>

Done (I hope).

Cheers,
joost.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads