Difference between Owned By and Assigned To

[rowan.bradley]

Can someone please explain the difference between Owned By and Assigned To?
If I create a new ticket and Assign it to X, it stays as New, not Assigned,
but Owned by X. This seems really weird. How can I assign it to X, but it
stay unassigned? There is no way that I can see on this screen to do
anything that will cause the ticket to show up as assigned in the ticket
list.

Thanks - Rowan



--
View this message in context: http://trac.10920.n7.nabble.com/Difference-between-Owned-By-and-Assigned-To-tp32981.html
Sent from the Trac Users mailing list archive at Nabble.com.

[Steffen Hoffmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12.01.2013 15:04, rowan.bradley wrote:
> Can someone please explain the difference between Owned By and Assigned To?
> If I create a new ticket and Assign it to X, it stays as New, not Assigned,
> but Owned by X. This seems really weird. How can I assign it to X, but it
> stay unassigned? There is no way that I can see on this screen to do
> anything that will cause the ticket to show up as assigned in the ticket
> list.

This one is about ticket-workflow.
You insist in having an assigned ticket status, so you'll need to define
it in your trac.ini's section titled [ticket-workflow]. Here is the Trac
default for 1.0:

[ticket-workflow]
accept = new,assigned,accepted,reopened -> accepted
accept.operations = set_owner_to_self
accept.permissions = TICKET_MODIFY
leave = * -> *
leave.default = 1
leave.operations = leave_status
reassign = new,assigned,accepted,reopened -> assigned
reassign.operations = set_owner
reassign.permissions = TICKET_MODIFY
reopen = closed -> reopened
reopen.operations = del_resolution
reopen.permissions = TICKET_CREATE
resolve = new,assigned,accepted,reopened -> closed
resolve.operations = set_resolution
resolve.permissions = TICKET_MODIFY

This defines the following five valid values for ticket status:
* 'new' (initial ticket status, hard-coded default meaning
"always there, even if not defined")
* 'assigned' - get there via the 'reassign' action from any status
but not from 'closed'
* 'accepted' - same as before, but action is named 'accept' here
Note: Therefor I do regularly delete that action and status
as redundant in my Trac applications, but YMMV.
* 'closed' - same as before, but special action 'resolve' is unique
for including the 'set_resolution' operation
Note: You won't want to delete or rename that status, because this is
the second ticket status, that is hard-coded in many places.
* 'reopened' - special for being the only alternative for 'closed'
tickets
Note: 'leave' is a special action, available in any ticket status
due to the special definition '* -> *'
Note2: I tend to obsolete 'reopened' as well by writing
reopen = closed -> new

accept vs. reassign or accepted vs. assigned is just to separate tickets
you adopt from tickets you've got assigned by someone else. It depends
on your local policy, if this matter to you. In my own applications it
doesn't, so only one action exists to reassign, and all tickets are in
'assigned' status, or further simplified: have only
'new' and 'closed' and actions to reassign, close and reopen.

The TracGuide has more on this topic, in your own TracWiki or at
http://trac.edgewall.org/wiki/TracWorkflow

Steffen Hoffmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlDx2SAACgkQ31DJeiZFuHfY0wCgsEe1vbWCYtoiAOrecC0muqM6
WE4An0NMp70uv9UksvHo7HKv3y7zLgk5
=r7cn
-----END PGP SIGNATURE-----

[RjOllos]

On Saturday, January 12, 2013 6:04:49 AM UTC-8, Rowan Sylvester-Bradley wrote:

Can someone please explain the difference between Owned By and Assigned To?
If I create a new ticket and Assign it to X, it stays as New, not Assigned,
but Owned by X. This seems really weird.

This confused me as well when I first started using Trac. A few years back I raised a ticket for the issue that drove a change that I had hoped would make this more clear:

http://trac.edgewall.org/ticket/8484

 

How can I assign it to X, but it
stay unassigned?

When you are creating a ticket, you are setting the owner, not assigning it. That was the thing I wanted to have clarified in #8484. What version of Trac are you using? The change in #8484 was applied in version 0.12.

I'm fairly sure that, although the workflow can be customized as hasienda has described, the initial state must be new. The workflow is constrained to have 'new' and 'closed' states, and the initial state of the ticket must be new.

 

There is no way that I can see on this screen to do
anything that will cause the ticket to show up as assigned in the ticket
list.

 If you don't have an 'assign' action, then you'll need to modify your workflow as hasienda has described. The default workflow in Trac has an assign action.