Linaro roadmap suggestion and requirement tracking
There are suggestions for the roadmap reporting that have not been pursued, some conflicting requirements etc that we have to track.
These should be discussed and prioritized individually before being worked on.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- Accepted for trunk
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Данило Шеган
Related branches
Related bugs
Sprints
Whiteboard
[asac, May 7 2012]: we should refresh requirements based on new JIRA roadmapping tool and the porting work lool is currently doing.
[danilo, June 22 2012] Will talk with Loic on new JIRA requirements in a few days, but this is so far obsolete.
These are the backlog items that currently are identified and need more information before we can work on them.
Add a card index page, so we can find any individual card easily. It looks like we want this so we should work out what this should look like.
Add work item graph on card view. I believe the final word on this was to not do it, we don't want work item details on the cards.
Add blueprint health checks. This was on the initial mock-up but we don't remember where the requirement came from.
Generate a list of all the "unlinked" BPs ie BPs without a roadmap ID. Do we want this?
In SLO the overview, per team and per person views should give lists of BPs which are unlinked to requirements. Do we want this?
Sort card blueprint table by targeted milestone and then by status. This conflicts with the requirement to have BPs needing attention (Blocked, Planned) float to the top while Completed BPs sink to the bottom.
