Tracking recurring work with cards is bothersome
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Linaro Roadmap |
New
|
Undecided
|
Unassigned | ||
Bug Description
Tracking recurring work through the roadmap process and the usual card workflow is bothersome:
- recurring work is requires less initial review: the need for the work should be explained as well as the plan for the allocation of resources and other than the reviewers inquiring about these two aspects there should not be much more reviewing
- recurring work requires fewer manual progress updates during execution: for example making releases already provides extensive reports on a weekly basis (release meeting wiki page) and also details of the release itself are copious and to the point
- recurring work deliverables at the end of the quarter usually are not usually final (in terms of stopping to recur). Some adjustment may be needed to improve the work as we move forward but usually the work goes on and deliverables will keep coming. Therefore closing out is rather useless unless there is a visible stop on delivering.
Dealing with cards for projects does not suit service-oriented deliverables such as release making. Recurring work requires new issue type and workflow for JIRA to align with the established work practices around this type of work.
