You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To monitor the health of projects in ASAM, it makes sense to have a dashboard automatically created from Git information. This information is useful for the ASAM Office, the TSC, CG:SIM, the project manager but also the project members.
Technical KPIs
Timeline
Active milestones on timeline with today marker
active = open milestones from git with percentage of completed issues
date from git
Days until release
Document freeze date minus today
Ticker / Announcements
Can be edited by a site admin
Can be solved by a specific issue in the repository (e.g.: parent repository)
Can be automatically resolved by a formatted email to a dedicated bot/recipient
Issues with most interest | issues to watch
Issues, with more than 2 subscribers & and action (Comment or created) in last 3 days. Issues with more Comments within 3 days are more important than with less comments. If there are the same amount of comments, the date of the comments are the decider
Data from git (Issues with comments, subscribers)
Merged MRs
The 3 newest merged MRs that are not older than 1 month. If there are less than 3 merged MRs a dummy is displayed, like "No merges since xx"
MergeRequests/Issues are displayed wich are ready for the CCB
Get Issues with label requires:CCBReview
useful links
project guide
proposal of the project
link to repository
link to documents ?
Contacts
ASAM Contact for the project
PL of the project
WG Leads ?
Next planned meetings
Get from the OpenXCalendar (html/ics)
The text was updated successfully, but these errors were encountered:
To monitor the health of projects in ASAM, it makes sense to have a dashboard automatically created from Git information. This information is useful for the ASAM Office, the TSC, CG:SIM, the project manager but also the project members.
Technical KPIs
The text was updated successfully, but these errors were encountered: