UI > Feature

ask for resolve-reason and comment after tasksCompleted / #299

Summary

v0.3- timing tasks
open
Jan 10, 2006
60 min ... 2 hours
Jan 10, 2006 / pixtur
Dec 11, 2006 / pixtur
 

Attached files

No files uploaded

in Quick Edit:

  • add form add a drop down list named "Change State" (task_change_state):
    • -- Do not change --
    • if state is open:
      • Complete as fixed
      • Complete as done
      • Close (because rejected)
      • Close (because bogous)
      • Close (because double)
      • Close (because cannot be reproduced)
    • if state is completed:
      • approve
      • reopen
    • if state is > completed:
      • reopen

With this we can quickly change the state of an task.

in context menu:

  • add new menu entry "change state" with the above options
  • This will be very tricky unless we have a better context menu

Any additional ideas or suggestions?

3 Comments

burger

Sep 5, 2006
View comment
Hello Tom!

How should this look like in detail?
  • New page with two fields for resolve-reason and comment?
  • Enhanced task form?
  • ...

pixtur

Sep 7, 2006

pixtur

Dec 11, 2006
What's missing...
tasksComplete and tasksApprove shoud render a small form similar to tasksEditMultiple and ask for resolve reason, resolve version and a comment. In a second step those data should be written to the DB.


 

Comment / Update