Opened 7 years ago

Closed 3 years ago

# Request ability to set a field as part of workflow

Reported by: Owned by: scottj@… Eli Carter normal AdvancedTicketWorkflowPlugin normal scottj@… 0.11

It would be really nice to be able to set a field as part of my ticket workflow. At the company I work for, we have a workflow that has an analysis stage. During the analysis, the developer assigned reviews the enhancement/defect and determines how much time he/she thinks it will require to implement the changes.

Right now, it's just assumed that the developer will fill in the 'estimatedhours' field themselves, then click the 'analyze' action to transfer it to another state. However, it would be better if the actual action to transfer to another state would read something like, 'analyze at _____ hours", and the developer would type in the number of hours he/she thinks it would require.

So, this request is simply to have some method of embedding a custom field into the action so that the workflow could set a custom ticket field upon making this action. In my example, the code to setup the operation might be:

   analyze = new -> analyzed
analyze.operation = set_field
analyze.field = ticket_custom.estimatedhours
analyze.units = hours


And the resulting actions might be:

• leave as new
• analyze at ______ hours (The estimated hours will be set. Next status will be 'analyzed'.)

+1

### comment:3 Changed 7 years ago by scottj@…

Hi retracile:

Any information on this? Do you know if this could be completed easily?

### comment:4 Changed 6 years ago by Eli Carter

Description: modified (diff)

### comment:5 Changed 3 years ago by Ryan J Ollos

Resolution: → duplicate new → closed

If you want to require a field to be filled in, it is suggested that you use a plugin such as DynamicFieldsPlugin. If you want to set a field to a specific value that is determined from the current state of the workflow, that might eventually be satisfied by a set_field operation suggested in #9502 and trac:#11452. It might be possible to move a field from the ticket properties to the workflow. We certainly don't want it in both places. That will be worked out in the aforementioned tickets.

### Modify Ticket

Change Properties