Emails from these addresses are auto-tracked as feed items (alerts, monitoring, etc.).
API Call Log (since last restart)
Loading...
Security issues
Advisories matched against what we actually run. Review once fixed; closed issues reopen only if they escalate.
One upgrade per library, per app. For each library you get the cheapest bump that stays in its current major version, and the version that clears everything. Counts cover the advisories that match our versions today. After an upgrade lands, the weekly dependency scan closes the rows, or press Review on a row to rescan straight away.
Platforms: one upgrade each
Same fix in many apps
One shared change (same target version) that teams can copy across repos.
Apps
Turnaround time
Alerts and support tickets that tech picked up, from the mail chains and Redmine. Clock runs 24x7 from the first mail. Unattended items are left out.
Trend
Breakdown
By week
Items
Needs details
These finished tickets had no code linked, so their story points were rated from the ticket text only. Add a GitLab merge request, commit or branch link, or a three line close-out note for work without code. The rater reads these entries on its next run.
Needs checking
These tickets got their story points from a big code change that may include code our developer did not write, such as a handed over proof of concept, a copied repo or generated code. Or the size looks too high. Read the analysis, then keep the points, use the proposed points, or explain what the developer actually built so the rater can re-rate.
Code with no ticket
This code has no ticket, so it earns no points. Link it to the ticket it belongs to, or let it go.
Code review findings
Every finding from the daily and weekly post-merge reviews. Review reads the current code in GitLab and tells you if it's fixed. Fixed is for a fix the code can't show, like a rotated token; say what fixed it. Fixed and It's alright close a finding until a later merge changes the same file and the review raises it again.