# Ticket #10464 (new enhancement)

Opened 7 months ago

## Accepting a ticket leaves it unowned.

Reported by: Assigned to: tom.knight@ucl.ac.uk bjornharrtell normal GridModifyPlugin normal 0.12

### Description

Great plugin, thanks.

One of my team noted that if he accepts a ticket (in the "Status" field) it remains unowned. I've added the "Owner" field to the [gridmodify] part of trac.ini thus:

[gridmodify]
fields = status,owner,priority,milestone,scope,blockedby,estimatedhours,component


... but of course this just means he's now able to accept the ticket and then type his username into the "Owner" field.

Is it possibly for the updating of "Status" to "Accepted" to also update "Owner" to the login of the user, at the same time?

Many thanks,

Tom.

## Change History

### 10/10/12 17:35:57 changed by rjollos

Do you have a custom workflow defined?

trac.ini

### 10/10/12 18:12:42 changed by anonymous

No, it's pretty standard.

My trac.ini is attached.

### 10/20/12 01:50:47 changed by rjollos

(In [12226]) Refs #10464: Replaced custom option parsing with a call to ListOption in the Trac API.

### 10/20/12 02:39:00 changed by rjollos

It looks like we'll need to invoke the workflow actions. This could take a bit of work, so I'm not sure when it will happen.

### 10/22/12 04:01:20 changed by rjollos

It looks like we'll need to invoke the workflow actions. This could take a bit of work, so I'm not sure when it will happen.

I worded that poorly. Rather, we need to specify an action that gets passed to apply_action_side_effects. At least, that is how it appears to work after a cursory inspection.

I suspect that the BatchModifyPlugin also has this problem, however it appears they've added the ticket workflow when integrating the plugin into the Trac core. Here is a screen capture from Trac 1.1.1dev:

### 10/22/12 13:23:23 changed by rjollos

Related to #4507.

### Add/Change #10464 (Accepting a ticket leaves it unowned.)

Change Properties