Skip to content

Update Developer Evangelist Request issue template: SAFE, labels, formatting, data collections

While reviewing an incident (internal), I've looked into updating the developer evangelist request issue template to raise awareness to create confidential issues for when the data is considered unSAFE.

While at it, I have also refreshed the issue template for more efficiency. I did not remove the DE budgets, scoring, audience descriptions - this needs another discussion for workflow changes.

This MR updates the following:

  1. Copy the HTML comment from the CFP-Meta issue template, with a friendly welcome at the header.
  2. Changes the requestor information, due date, event details into tables (in the hope that scrolling the template gets shorter)
  3. Request type: Change to three big bullets: Content, Speaking, Speaker Enablement, and sub-types. Add URL references when applicable to help team members decide.
  4. Add a note about community response workflows, that are different request types.
  5. Add URL section at the bottom, to use short URL references in the issue template. This increases readability when filling out the details.
  6. Add default quick actions for external request types: Labels, Due date, assignees, etc. including HTML comments to help.
  7. Add a commented /confidential quick action, asking the requestor to ensure the data is SAFE, otherwise making it confidential at creation time.
  8. Formatting and readability updates, adding team FYI tags.

FYI @johncoghlan @sugaroverflow

Merge request reports

Loading