Following the discussion in the TSC call https://wiki.onap.org/display/DW/TSC+2019-04-11 it seems to me that managing the project status and scorecards in the wiki is like re-implementing an issue tracking system with post-it notes.
Suggestion: Raise JIRA tickets in each ONAP project for each milestone and/or release requirement - JIRA tickets are assignable to people for implementation and follow-up. - JIRA tickets communicate priority, completion status and dates. - JIRA tickets can be queried and filtered to provide summary reports. - JIRA tickets can be linked to other JIRA tickets for dependencies, blockers and related issues. That appears to cover all the meanings of all rows and columns and colour-highlights in pages like - https://wiki.onap.org/display/DW/Project+Status+in+Dublin+Release - https://wiki.onap.org/display/DW/Dublin+Release+Requirements Maybe there could be new JIRA configs to assist, e.g. - Issue Types for Scorecards - project Components for Milestones - Labels for cross-cutting concerns like needing TSC approval and being POC Based on all that JIRA ticket information, a Kanban board will show visually when a Milestone or Release is Done! The wiki can then go back to being a place for documentation and instructions and in-depth explanations, rather than being constantly updated merely to change red-to-yellow-to-green etc. Keong -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4826): https://lists.onap.org/g/onap-tsc/message/4826 Mute This Topic: https://lists.onap.org/mt/31037942/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
