Draft: Monitor:Respond Weekly Update - W33 - Aug-14-2023
< previous update | next update > |
---|
Current team focus
Summarize what the team is currently focused on. Keep it as short as possible while conveying key information.
Milestone plan: add link to milestone planning issue
Highlights
- Sorting and loading state for Service Desk issue list is available on staging. With next/previous page handlers about to merge, we are finishing this week with 95% of the functionality available for testing.
🎉
Stats
Going into the week
Capacity: 83% (70% of frontend, 90% of backend)
For the week of Monday, 2023-08-14.
-
frontend: max of 2 engineers, 5 days in week
7(days) = 10(days) - 3(PTO)
-
backend: max of 4 engineers, 5 days in week
18(days) = 20(days) - 2(PTO)
Data from: Monitor:Respond Group Calendar, via Google App Scripts
27 Rollover issues from %16.3
%16.3 rollover:
-
Ticket is a work item type (gitlab-org/gitlab#414352)
tristan.read
-
Toggle between Work Item & Old style Issue Views (gitlab-org/gitlab#414313)
tristan.read
-
Consider removing unncessary documentation rela... (gitlab-org/gitlab#411372)
tristan.read
-
Clean up presentation of items in incident high... (gitlab-org/gitlab#360009)
tristan.read
-
Extract shared parts for Issues and Service Des... (gitlab-org/gitlab#418920 - closed)
psjakubowska
-
[Feature flag] Roll out service_desk_vue_list (gitlab-org/gitlab#415385 - closed)
psjakubowska
-
Update filter and sort bar in Service Desk List (gitlab-org/gitlab#413092 - closed)
psjakubowska
-
[Feature flag] Rollout of `remove_monitor_metrics` (gitlab-org/gitlab#399248)
psjakubowska
-
Monitor Stage Deprecations: Remove Metrics from... (gitlab-org/gitlab#351390)
psjakubowska
-
test-prof: Remove `factory_default: :keep` metatag (gitlab-org/gitlab#418776)
splattael
-
Remove "grace period" for cops added/changed in... (gitlab-org/gitlab#416867 - closed)
splattael
-
Add `read_observability` and `write_observabili... (gitlab-org/opstrace/opstrace#2243 - closed)
splattael
-
Use .rubocop_todo/**/*.yml for HAML exclusions (gitlab-org/gitlab#415330)
splattael
-
Error Tracking: Remove old Postgres backend (gitlab-org/gitlab#414933)
splattael
-
Upgrade email_reply_trimmer to latest version t... (gitlab-org/gitlab#412480)
splattael
-
Clean up RuboCop cops after Ruby 3 release (gitlab-org/gitlab#389422 - closed)
splattael
-
Metrics: Remove service ping metrics (gitlab-org/gitlab#397136)
syasonik
-
Allow Prometheus' metrics dashboard and incomin... (gitlab-org/gitlab#338838)
syasonik
-
Ticket is a work item type (gitlab-org/gitlab#414352)
tristan.read
-
Use `service_desk_settings.service_desk_enabled... (gitlab-org/gitlab#412673)
ck3g
-
Migrate data from `projects.service_desk_enable... (gitlab-org/gitlab#412671)
ck3g
-
Update value in sevice_desk_settings.service_de... (gitlab-org/gitlab#412670)
ck3g
-
Move service_desk_enabled column to service_des... (gitlab-org/gitlab#36126)
ck3g
-
Metrics: Remove ignore rules for removed columns (gitlab-org/gitlab#397146)
rkadam3
-
Metrics: Delete models & database tables/columns (gitlab-org/gitlab#397142)
rkadam3
-
Metrics: Delete usage in services, finders, etc (gitlab-org/gitlab#397139 - closed)
rkadam3
-
Monitor:Respond Weekly Update - W32 - Aug-07-2023 (#264 - closed)
francoisrose
Data from: GitLab REST API. Contains open issues which are in a prior milestone & assigned to a grouprespond engineer.
16.4 focus area distribution
92% typefeature | 8% typebug |
---|---|
42% featureenhancement 42% featureaddition 17% w/o sub-type |
100% bugux |
31% Priority Widget (gitlab-org&10787) | 31% w/o epic | 8% Participants in Service Desk (gitlab-org&3758) | 8% Service Desk: Add external email participants t... (gitlab-org&10636 - closed) | 8% Service Desk "Ticket" Work Item Type (gitlab-org&10419) | 8% Improve Service Desk List (gitlab-org&10706) | 8% Service Desk: Migration to Work Items (gitlab-org&10772) |
---|---|---|---|---|---|---|
100% w/o eng label | 100% w/o eng label | 100% backend frontend | 100% w/o eng label | 100% w/o eng label | 100% w/o eng label | 100% backend frontend |
End of week progress snapshot
~20% complete of 16.4 scheduled work
- 0% - of scheduled issues without an epic
- 100% - of scheduled issues from epic: Service Desk: Migration to Work Items (pre-migr... (gitlab-org&11204)
- 0% - of scheduled issues from epic: Service Desk Issue list enhancements (gitlab-org&11203)
- 0% - of scheduled issues from epic: Priority Widget (gitlab-org&10787)
- 0% - of scheduled issues from epic: Service Desk "Ticket" Work Item Type (gitlab-org&10419)
- 0% - of scheduled issues from epic: Service Desk: Add external email participants t... (gitlab-org&10636 - closed)
- 0% - of scheduled issues from epic: Participants in Service Desk (gitlab-org&3758)
Percentage is a rough estimate and could be quite wrong. The calculation codifies @syasonik
's mental model for ~% completion, based on workflow labels, open MRs, and domain labels.
More info...
Standalone issues - 0% complete
Issue | Status | ~% Complete |
---|---|---|
Service Desk issue moved to project with Servic... (gitlab-org/gitlab#422303) Type: typebug Domains: |
@msaleiko No grouprespond assignee workflowready for development |
0% |
[Feature flag] Cleanup usage_data_incident_mana... (gitlab-org/gitlab#421861) Type: typemaintenance maintenanceremoval Domains: |
No assignee workflowready for development |
0% |
Fix keyboard navigation with date token in filt... (gitlab-org/gitlab#420266) Type: typebug bugux Domains: |
No assignee workflowready for development |
0% |
Drop `projects.service_desk_enabled` column (gitlab-org/gitlab#412675) Type: typefeature featureaddition Domains: database |
@ck3g workflowready for development |
2% |
Service Desk: Improve GitLab Support Bot user p... (gitlab-org/gitlab#412616) Type: typefeature featureenhancement Domains: |
No assignee workflowready for development |
0% |
Add alert type to webhooks (gitlab-org/gitlab#299588) Type: typefeature Domains: |
No assignee workflowready for development |
0% |
Service Desk: Migration to Work Items (pre-migration) - 100% complete
Issue | Status | ~% Complete |
---|---|---|
Allow (work item) Service Desk ticket to be ass... (gitlab-org/gitlab#420862) Type: typefeature featureaddition Domains: backend frontend documentation database Possible action items required- check workflow label for accuracy - workflow label is absent |
No assignee workflowready for development Relevant MRs: (1) Merged MRs (1): gitlab-org/gitlab!127482 (merged) |
100% |
Service Desk Issue list enhancements - 0% complete
Issue | Status | ~% Complete |
---|---|---|
Update illustrations for Service Desk list (gitlab-org/gitlab#420139 - closed) Type: typefeature featureenhancement Domains: |
No assignee workflowready for development |
0% |
Priority Widget - 0% complete
Issue | Status | ~% Complete |
---|---|---|
Instrument Priority Widget (gitlab-org/gitlab#416792) Type: typefeature Domains: |
No assignee workflowready for development |
0% |
Priority is sortable (gitlab-org/gitlab#414538) Type: typefeature featureenhancement Domains: |
No assignee workflowready for development |
0% |
Priority is filterable (gitlab-org/gitlab#414537) Type: typefeature featureenhancement Domains: |
No assignee workflowready for development |
0% |
Create the priority widget (gitlab-org/gitlab#414536) Type: typefeature featureenhancement Domains: |
No assignee workflowready for development |
0% |
Service Desk "Ticket" Work Item Type - 0% complete
Issue | Status | ~% Complete |
---|---|---|
Create / change service desk tickets via API (gitlab-org/gitlab#415383 - closed) Type: typefeature featureaddition Domains: |
No assignee workflowready for development |
0% |
Service Desk: Add external email participants to service desk via quick action - 0% complete
Issue | Status | ~% Complete |
---|---|---|
Instrument Usage Ping on how people add partic... (gitlab-org/gitlab#412054 - closed) Type: typefeature featureaddition Domains: |
No assignee workflowready for development |
0% |
Participants in Service Desk - 0% complete
Issue | Status | ~% Complete |
---|---|---|
External participants are notified when added a... (gitlab-org/gitlab#299261 - closed) Type: typefeature featureaddition Domains: backend frontend UX |
No assignee workflowready for development |
0% |
Contributions on: 68 merge_requests, 38 issues, 4 work_items, 7 epics
Contributions span from 2023-08-11 to 2023-08-19.
tristan.read focus areas
- Type: 43% typemaintenance, 35% typebug, 5% typefeature, 18% other (<3% each)
- Group: 33% groupoptimize, 23% groupux paper cuts, 18% groupthreat insights, 13% grouprespond, 8% groupfoundations, 3% grouppackage registry, 5% other (<3% each)
- Category: 5% Category:Status Page, 3% Category:Container Registry, 93% other (<3% each)
- Work item: 80% ~"merge_requests", 20% issues
grouprespond contributions
merge_requests
- Reduce status page update frequency : commented on (1), opened (1) issues
- Tuesday 2023-08-15 05:07 UTC - `gitlab-org/gitl... (gitlab-org/quality/engineering-productivity/master-broken-incidents#3308 - closed) : commented on (3)
other contributions
merge_requests
- Explain this Vulnerability: Changed badge : commented on (22), accepted (4), approved (4) issues
- Format graphql files with prettier (gitlab-org/gitlab#227280 - closed) : commented on (1), closed (1)
- Decrease upgrade frequency in Status Page (gitlab-org/frontend/renovate-gitlab-bot#45 - closed) : commented on (3)
psjakubowska focus areas
- Type: 55% typefeature, 21% typemaintenance, 4% typebug, 3% typeignore, 18% other (<3% each)
- Group: 71% grouprespond, 4% groupproject management, 4% groupux paper cuts, 3% groupsource code, 18% other (<3% each)
- Category: 56% Category:Service Desk, 3% Category:Source Code Management, 41% other (<3% each)
- Work item: 79% ~"merge_requests", 14% issues, 5% ~"work_items", 1% other (<3% each)
grouprespond contributions
merge_requests
- Service Desk List - handle next and previous : commented on (39), opened (5), approved (2), closed (1)
- Reduce status page update frequency : commented on (1) issues
- Ticket is a work item type (gitlab-org/gitlab#414352) : commented on (1)
- Draft: Monitor:Respond Weekly Update - W33 - Au... (#265 - closed) : commented on (2) epics
- Improve Service Desk List (gitlab-org&10706) : commented on (1)
other contributions
merge_requests
- Fixes comma placement for codeowners : commented on (6), approved (3)
- Draft: test(e2e): Use cypress-axe to check : commented on (1) issues
- Define technical strategy to implement automati... (gitlab-org/gitlab#420593 - closed) : commented on (5)
- Improve components accessibility documentation (gitlab-org/gitlab-services/design.gitlab.com#1666) : commented on (1)
- August 2023 Showcase forecast (gitlab-com/ops-sub-department/ops-engineering-management#242 - closed) : commented on (1) work_items
- gitlab-org/gitlab#421946 (closed) : opened (4)
splattael focus areas
- Type: 61% typemaintenance, 24% typefeature, 4% typebug, 12% other (<3% each)
- Group: 50% grouprespond, 7% groupprovision, 6% groupide, 5% groupsource code, 4% groupdatabase, 4% groupimport and integrate, 25% other (<3% each)
- Category: 22% Category:Service Desk, 6% Category:Metrics, 6% Category:Remote Development, 5% Category:Source Code Management, 4% Category:Database, 58% other (<3% each)
- Work item: 80% ~"merge_requests", 20% issues
grouprespond contributions
merge_requests
- Route alert notifications through single : commented on (22), approved (5), accepted (4)
- Track reasons why things fail : commented on (19) issues
- Tuesday 2023-08-15 05:07 UTC - `gitlab-org/gitl... (gitlab-org/quality/engineering-productivity/master-broken-incidents#3308 - closed) : commented on (1)
- Feature flags requiring attention for group::re... (gitlab-org/quality/triage-reports#13508 - closed) : commented on (1)
other contributions
issues
- Danger: Skip warning about use of `let_it_be` f... (gitlab-org/gitlab#422340) : commented on (7), opened (1), closed (1)
- GitlabSecurity/SqlInjection is giving false-pos... (gitlab-org/ruby/gems/gitlab-styles#61) : commented on (4)
- Ruby upgrades - Discussions on how to improve t... (gitlab-org/quality/engineering-productivity/team#270 - closed) : commented on (1)
- Upload custom emojis via CI (custom_emoji/custom_emoji#6) : commented on (3), opened (2) merge_requests
- Draft: Add QA/FabricateUsage cop : commented on (27), accepted (2), approved (3)
- Memoize ability_map, conditions, : commented on (1)
syasonik focus areas
- Type: 97% typemaintenance, 3% other (<3% each)
- Group: 100% grouprespond
- Category: 23% Category:Metrics, 19% Category:Incident Management, 58% other (<3% each)
- Work item: 100% ~"merge_requests"
grouprespond contributions
merge_requests
- Draft: Add external issue author to graphql : opened (3), commented on (27), closed (1)
other contributions
ck3g focus areas
- Type: 40% typemaintenance, 38% typefeature, 16% typebug, 5% other (<3% each)
- Group: 48% grouprespond, 7% ~"group::authentication and authorization", 7% groupproject management, 7% groupanti-abuse, 7% groupcode review, 4% groupproduct analytics, 4% groupscalability, 3% groupthreat insights, 3% groupimport and integrate, 3% grouptenant scale, 3% groupsource code, 5% other (<3% each)
- Category: 19% Category:Service Desk, 11% Category:Metrics, 7% Category:Team Planning, 3% Category:Vulnerability Management, 3% Category:Integrations, 3% Category:Groups & Projects, 3% Category:Error Tracking, 3% Category:Source Code Management, 49% other (<3% each)
- Work item: 93% ~"merge_requests", 5% issues, 1% other (<3% each)
grouprespond contributions
merge_requests
- Delete base stage class, URL validator class : commented on (18), approved (3), accepted (2), closed (1), opened (7) issues
- Ticket is a work item type (gitlab-org/gitlab#414352) : commented on (2), opened (1)
- Tuesday 2023-08-15 05:07 UTC - `gitlab-org/gitl... (gitlab-org/quality/engineering-productivity/master-broken-incidents#3308 - closed) : commented on (1)
other contributions
merge_requests
- /assign @ameyadarshan : commented on (22), approved (10), accepted (5) epics
- 👧 Work Items - Relationships (gitlab-org&6286) : commented on (1)
rkadam3 focus areas
- Type: 83% typemaintenance, 11% typefeature, 6% typebug
- Group: 94% grouprespond, 6% groupthreat insights
- Category: 72% Category:Metrics, 11% Category:Service Desk, 17% other (<3% each)
- Work item: 100% ~"merge_requests"
grouprespond contributions
merge_requests
- Delete base stage class, URL validator class : commented on (9), opened (6), approved (2)
francoisrose focus areas
- Type: 9% typefeature, 7% typemaintenance, 6% typeignore, 4% typebug, 74% other (<3% each)
- Group: 70% grouprespond, 9% groupproduct planning, 20% other (<3% each)
- Category: 22% Category:Service Desk, 78% other (<3% each)
- Work item: 80% issues, 20% epics
grouprespond contributions
issues
- Ops Showcase Presentation: Service Desk: Automa... (gitlab-org/ci-cd/section-showcases#35 - closed) : commented on (1)
- Update CES Service Desk to include triage featu... (gitlab-org/gitlab#421217 - closed) : commented on (17), closed (2), opened (3)
- Tuesday 2023-08-15 05:07 UTC - `gitlab-org/gitl... (gitlab-org/quality/engineering-productivity/master-broken-incidents#3308 - closed) : commented on (5), closed (1)
- Feature flags requiring attention for group::re... (gitlab-org/quality/triage-reports#13508 - closed) : closed (1), commented on (2)
- Monitor:Respond Weekly Update - W32 - Aug-07-2023 (#264 - closed) : closed (1), commented on (2) epics
- Service Desk: Migration to Work Items (gitlab-org&10772) : commented on (1)
- Improve Service Desk List (gitlab-org&10706) : commented on (1)
- Modernized Service Desk Issue list (gitlab-org&11202 - closed) : opened (1)
other contributions
epics
- 👧 Work Items - Relationships (gitlab-org&6286) : commented on (5)
- Service Desk: Migration to Work Items (post-mig... (gitlab-org&11205) : opened (1)
- Service Desk: Migration to Work Items (pre-migr... (gitlab-org&11204) : opened (1)
- Service Desk Issue list enhancements (gitlab-org&11203) : opened (1) issues
- Edit security policy button breaks if project p... (gitlab-org/gitlab#420812 - closed) : commented on (1)
- August 2023 Showcase forecast (gitlab-com/ops-sub-department/ops-engineering-management#242 - closed) : commented on (2)
- [ENG] Find all instances of where we use Monito... (gitlab-com/marketing/digital-experience/buyer-experience#2744 - closed) : commented on (1)
- FY24 Q3 OKR discussion (#258 - closed) : commented on (3), closed (1)
Data from: Scraped from activity page for each user. Activities which don't support labels are mostly ignored.
Relevant links
- Current Planning Issue
- Async Retrospectives
- Internal dogfooding adoption (chart)
- Dogfooding by feature (table)
- Support Help Requests
- Ops Department Status Updates
This update was generated by the weekly_update script in gitlab-org/monitor/respond. Highlights are manually curated.
How does it work?
Where does the content come from?
Highlights are added manually; everything else is pulled from GitLab, Google, Grafana, etc.
How does it get there?
- Every Friday, a scheduled pipeline creates the issue for the next week, and it updates the issue for the current week.
- When a new issue is created, only a few details are included in the description about what might be expected for the week. A comment thread is added where highlights can be collected to be autofilled into the description later in the week.
- When the issue is updated, the highlights thread will be collected as a list and added to the issue description. An detailed overview of progress on the milestone will also be included.
How do I make changes?
To this specific issue
This specific issue: Add content directly to the issue description, or you can add highlights by commenting on the highlights thread.
Format
Static content: Update weekly-update.md. Add any static content to the file to include it in the issue description when the issue is created.
Dynamic content: Rearrange the REPLACE-ME
placeholder HTML comments. Placeholder comments can be either singleline or multiline. The placeholders are replaced by script-aggregated content.
- Required attributes:
-
section
: all-caps name given to a chunk of markdown generated by the weekly_update script.-
NAVIGATION
-> Link to previous/next update issue -
CAPACITY
-> PTO breakdown for Monitor:Respond team for the week -
ERROR-BUDGET
-> Current state of respond error budget -
ISSUE-DISTRIBUTION
-> Breakdown of team's focus by type label & epic -
PROGRESS-SUMMARY
-> Estimated % completion of scheduled issues by epic -
PROGRESS-DETAIL
-> Estimated % completion of each individual scheduled issue -
TEAM-ACTIVITY
-> Aggregated contributions for each team member over the last week -
ROLLOVER
-> Issues assigned to team members in expired milestones -
TEAM-LINKS
-> Link to planning issue & other team-specifics that change week to week -
QUICK-ACTIONS
-> Assigns milestone & other team-specifics that change week to week -
HIGHLIGHTS
-> List of comments from highlight thread (oldest thread to include the word "highlight" in the first comment)
-
-
action
: determines when the comment will be replaced in the issue description.-
CREATE
- replaced when the issue is created -
UPDATE
- replaced at the end of the week
-
-
- Singleline format:
<!-- REPLACE-WITH-<section>:<action> -->
- Multiline format:
-
<!-- REPLACE-WITH-<section>-START:<action> --> Anything here will also be replaced when the script runs. <!-- REPLACE-WITH-<section>-END:<action> -->
-
Adding threads: Add a multiline placeholder with section
of THREAD
. Content inside the block will be added as a thread on the issue, and it can include other placeholders.
Content
Run the Generate detailed weekly update issue
to trigger an update. Once an update has run, the pipeline can be run many
times without consequence to the existing issue. Refer to Format > Dynamic content
for the syntax needed
to regenerate sections of the issue.
To modify how the content itself is generated, refer to weekly_update/README.md
.