Tasks vs Issues, for v7 port
The currently implemented (6.1) workflow for Service Management uses Issues + Tasks:
1) Client opens an Issue
2) Service Team triages Issues and opens a Task
3) Task is planned/scheduled, completed and Closed
4) Issue is also (automatically) closed
My current experience is that the (Issues + Tasks) solution can be confusing for users.
Using only one of either Issues or Tasks would also enable for then Kanban to give a unified view of the open Incidents .
For the migration to v7, I'm considering using Issues only.
That means:
* using Timesheets on Issues
* extending this timesheet to also record materials spent
* adding other fields relevant for the intervention's service report.
* preventive maintenance would be recorded as Issues of a special category
* Tasks would be used only for new Installation Projects.
Comments on this design and other migration considerations would be appreciated.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Daniel Reis
- Direction:
- Needs approval
- Assignee:
- Daniel Reis
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Daniel Reis
Related branches
Related bugs
Sprints
Whiteboard
Joël@camptocamp: I'm in favor of this new design. Note that for timesheet, it'll be good to have a similar solution as we've made for timesheet on tasks (https:/
One question : What about time/consumption on issues ? Does this work as in task ? It'll be very apprciated.
