•  
     
    story #12538 set values on fields given conditions
Summary
tracker admin
set values on fields given conditions

I can identify late tasks, tasks that whose end_date is over the due_date.

This should be added as a part of the workflow post-action of a given transition (e.g. on "Done").

There are two approches there:

  • numeric fields + formula
    • eg: The integer field [overdue by] is set to [=end_date - due_date]
  • list field + condition
    • eg. The list/checkbox field [post-mortem] is set to [late] when [end_date] [>] [due_date]

In both cases, a special care should be taken to the order of conditions are fields might get a value by another post action of the same transition.

 

Empty
Empty
Status
Empty
Ready (stalled)
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#12538
Manuel Vacelet (vaceletm)
2018-11-20 17:24
2018-11-20 17:24
4210

References
Referencing story #12538

Artifact Tracker v5

epic #2047 Tracker