Creating support Dev Pulse page
Why is this change being made?
Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency. Please add the details saying why, not just what in this section. Example:
We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.
Relates to https://gitlab.com/gitlab-com/support/support-ops/support-ops-project/-/issues/970
Author and Reviewer Checklist
Please verify the check list and ensure to tick them off before the MR is merged.
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
For transparency, share this MR with the audience that will be impacted. -
Team: For changes that affect your direct team, share in your group Slack channel -
Department: If the update affects your department, share the MR in your department Slack channel -
Division: If the update affects your division, share the MR in your division Slack channel -
Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR - For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter
-
Commits
- Creating support Dev Pulse page
Merge request reports
Activity
added HandbookContent label
requested review from @vparsons
assigned to @jcolyer
- Resolved by Val Parsons
- Resolved by Val Parsons
- Resolved by Val Parsons
- Resolved by Val Parsons
@jcolyer Thank you for the work done to put this update together.
It is only now that I see the nuance of the RFHs being included in this process as it was not part of my original proposal.
While I can see benefits of tracking the time that an associated RFH is open, it doesn't make sense for the tickets to be treated in the same way as a bug issue (or a feature request). RFHs may need excluding from the Sep 1st implementation while we consider what aids the workflow. Removing them from the 'normal' ticket views would be contra to our way of working with the RFH tickets.
- Resolved by Val Parsons
- Resolved by Val Parsons
Anything more you need from me on this @jcolyer ?
- Resolved by Val Parsons
@jcolyer I tested Dev Pulse on a bunch of tickets. There was a ticket where the customer responded after I applied the macro, but the ticket didn't re-appear in my queue. Is it possible to make such tickets re-appear in the Assignee's queue?
Example ticket: https://gitlab.zendesk.com/agent/tickets/533792
reset approvals from @vparsons by pushing to the branch