Skip to content

Alter Data Triage page

Radovan Bacovic requested to merge rbacovic-master-patch-79351 into master

Why is this change being made?

Need to alter 2 things:

  1. Connect Triage page with the provider contact after the MR is finished !91174 (diffs) to provide an easier way to contact 3rd party provider when needed
  2. Improve the Triage page to explain the issue solving life cycle. The inspiration comes from Weekly Data Engineering Team Meeting 
Triager effort lifecycle: how to be more efficient and how to determinate time and effort. Let say we have this scenario:
- I evident one tricky issue
- It is the first time I see it - need some time to become familiar with the product/pipeline
- Issue is complex and requires further analysis and communication/collaboration with other team members
- Day passed very quickly and I am moving forward with my OKRs
- Next week on the Triage I am occupied with other things
- How to overcome this:
    - To spillover Triage work to day after my Triage?
    - To take over that works to another Triager coming after me?
    - Something else?
Probably I missed some piece of context here to catch up and get the full picture, but fully motivated to try to find the best way for this

Radovan: spillover when it is super important to be efficient. Of course, need to add an issue to maybe change the handbook

Author Checklist

  • Provided a concise title for the 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.
  • Assign reviewers for this change to the correct DRI(s)
    • 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 in 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.
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR.
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports