On 1/08/2014 5:52 PM, RjOllos wrote:
On Thursday, July 31, 2014 4:02:25 AM UTC-7, Mike Dewhirst wrote:
I have a problem with the terminology used in Trac and I wonder how to
fix it so it makes sense to me.
In Trac out of the box ...
"Owner" is the developer to whom the ticket is assigned for work.
In my project ...
"Owner" is the person who wants the ticket payload - the fixed bug or
the enhancement - IOW the person who accepts or rejects the payload.
So the fix seems to me to change the Trac "Owner" to "Developer"
(presumably in the template) and add another field/column for my
project's "owner", perhaps "customer".
However, it looks like a major adjustment and maybe going against the
flow because I need to use the workflow plugin
Does anyone have any ideas?
Thanks
Mike
You can use an ITemplateStreamFilter to replace "Owner" with
"Developer". See example here:
https://groups.google.com/d/msg/trac-users/EOfAlxo-dMc/yjMQ3m7-nXYJ
Ryan
Had a quick look and that seems a good start. I'm happy to change Trac's
owner into "Developer" because that doesn't change any meaning as far as
I'm concerned.
I also looked at those two tickets you mentioned and I reckon I should
wait and see.
I'm now thinking the Cc: field might be what I'm looking for anyway. If
the dev adds a comment or resolves the ticket as "testing" (as per the
workflow) my owners for that ticket in Cc: will get an email anyway. For
example, if the dev has a question, it can be added as a comment and
they will all be able to respond. The dev might have to give out an
email address to respond to though.
I would love to keep it simple.
Thanks
Mike
In the future we might have am ICustomFieldTypeProvider interface that
would allow new custom field types to be defined. That would allow for a
"restricted list of valid users" type, which could be a select list
containing the list of users with valid sessions (it would be like the
owner field in the ticket workflow when [ticket] restrict_owner = true).
That might help with defining your "customer" ticket field.
http://trac.edgewall.org/ticket/11469#comment:4
For now, you may be right that using the workflow is the better way to
accomplish this. A related enhancement might support assigning a value
to a field in a workflow action (e.g. your "customer" field).
http://trac.edgewall.org/ticket/11452
--
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 [email protected]
<mailto:[email protected]>.
To post to this group, send email to [email protected]
<mailto:[email protected]>.
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/trac-users.
For more options, visit https://groups.google.com/d/optout.
