Clarify the issue types that require Quad Planning
Why is this change being made?
It is currently unclear what type of issues require Quad Planning. Based on this slack discussion, it appears that the SETs mostly do Quad Planning for feature
issues and struggle to do it for other issues due to capacity constraints. Some also provide input on S1
bug
issues. This MR clarifies what issues quad-planning::ready
label should be applied to.
Author Checklist
-
Correct MR template applied (e.g blog post) -
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 -
Assign this change to the correct DRI - If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
- 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 relate to any part of the project other than updates to content and/or data files please make sure to ping
@gl-static-site-editor
in a comment for a review and merge. For example changes to.gitlab-ci.yml
, JavaScript/CSS/Ruby code or the layout files.
For help with failing pipelines reach out in #mr-buddies in Slack
Edited by Sanad Liaquat