Add Knowledge::P* labels

Why is this change being made?

Last month we had a following discussion on the retrospective:

1. Himanshu: We assign issues to “%Next 2-3 Milestones” or “%Next 4-6 Milestones” but we need to look at issues in those milestones monthly, otherwise issues stay in those milestones forever.
   1. Naman: we can have a due date.
   2. Himanshu: I like that idea.
   3. Vlad: question to the team: how do you raise issues to product.
   4. Himanshu: why don’t we just use priority labels? Right now we only using this for bugs.
   5. Vlad: we can define Knowledge::P1/P2/…
   6. Naman: we an use PL1/PL2 as “planning priority”
   7. Himanshu: I like the idea with due dates, but people may think we missing all the deadlines.
      1. Matthew Macfarlane: Yes we need to be careful with this. It can put expectations both internal and external that adds additional pressure.
   8. Naman: we can open an issue and discuss

After some discussion with @mmacfarlane we decided that we want to try using priority labels starting from the next milestone.

The idea is to also use them outside of the milestone for keeping track of issues:

• when someone thinks we should prioritize an issue, they add the priority label
• when selecting issues for the upcoming milestone PM and EM first review P1 issues, then P2, etc...

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
• 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

• Add Knowledge::P* labels

---