New tickets should be able to default owner to the current user

[lashchev@…]

We use Trac very actively to manage our Dev tasks and not just as bug tracking system. We have much more tasks than defects or enhancements and in most of the cases Devs are filing tasks for themselves.

It would be very useful if "default_owner" ticket setting could support value like "$USER" meaning that currently logged-in user is pre-selected in the owner field on the new ticket form.

[ebray]

This could also be accomplished with a very simple plugin.

[anonymous]

Replying to ebray:

This could also be accomplished with a very simple plugin.

There does not seem to be a pre-written plugin for accomplishing this task. I too see a value in supporting the $USER variable in the default_owner section of the ini rather than hacking it into the site template.

[Christian Boos]

PatchWelcome.

[anonymous]

bit ugly, and only tested in limited circumstances, but might help someone…

trac/ticket/model.py

@@ -217 +217 @@
             # _something_ else, even if that something else is blank.
             self['owner'] = default_to_owner
 
+        if self.values.get('owner') == '< reporter >':
+            default_to_reporter = ''
+            if self.values.get('reporter'):
+                default_to_reporter = self['reporter']
+            self['owner'] = default_to_reporter
+
         # Perform type conversions
         values = dict(self.values)
         for field in self.time_fields:

[Christian Boos]

Or just ... self['owner'] = self.values.get('reporter', '')?

I'm no fan of such kind of special values, but we started the trend with < default >, so…

[Ryan J Ollos]

Requested also in ​SO:24675086. Implementing the proposed changes in #2045 will allow set_owner_to_self to be used in the <none> -> new transition (comment:38:ticket:2045).

[Ryan J Ollos]

This ticket will be closed as a duplicate of #2045, but before closing this ticket I'll provide a [ticket-workflow] recipe.

[Ryan J Ollos]

With #2045 implemented, the default create actions are:

create = <none> -> new
create.default = 1
create_and_assign = <none> -> assigned
create_and_assign.label = assign
create_and_assign.operations = may_set_owner
create_and_assign.permissions = TICKET_MODIFY

To have the create action assign to the current user, just add:

create.operations = set_owner_to_self

Renaming the action might be appropriate, putting the ticket into either the assigned or accepted state:

create_and_accept = <none> -> accepted
create_and_accept.label = accept
create_and_accept.default = 1
create_and_accept.operations = set_owner_to_self

See ticket #11856 for proposed changes that will replace the [ticket] default_owner option, and particularly comment:3:ticket:11856.

[David Banner <dbwonderchild@…>]

There does not seem to be a pre-written plugin for accomplishing this task. I too see a value in supporting the $USER variable in the default_owner section of the ini rather than hacking it into the site template.

Is the $USER variable supported in the default_owner section yet?

[Ryan J Ollos]

Replying to David Banner <dbwonderchild@…>:

Is the $USER variable supported in the default_owner section yet?

No, and it probably won't be added. You can achieve the equivalent in Trac 1.1.3 and later as described in comment:13.