Changes between Initial Version and Version 4 of Ticket #6921


Ignore:
Timestamp:
Mar 16, 2011, 2:45:42 PM (12 years ago)
Author:
Eli Carter
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #6921

    • Property Cc scottj@… added; anonymous removed

  • Ticket #6921 – Description

    initial v4  
    11It 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. 
    22
    3 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. 
     3Right 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. 
    44
    55So, 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:
    … …  
    1515
    1616   * leave as new
    17    * analyze at ______ hours (The estimated hours will be set. Next status will be 'analyzed'.)
     17   * analyze at `______` hours (The estimated hours will be set. Next status will be 'analyzed'.)
    1818