2021-06-21 - Quad Planning Issues for Fulfillment

Hi @gl-quality/fulfillment-qe

Please quad-plan the following issues:

Group: ~"group::purchase"

• gitlab-org/customers-gitlab-com#3268 (closed) [BE] Customers should only be able to renew 15 days before subscription expiration date Category:Purchase, Deliverable, backend, devopsfulfillment, ~"group::purchase", sectionfulfillment, workflowready for development %14.1
• https://gitlab.com/gitlab-org/gitlab/-/issues/333698 (confidential) ~"(confidential)" %"(confidential)"
• https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/3255 (confidential) ~"(confidential)" %"(confidential)"
• gitlab-org/customers-gitlab-com#3206 (closed) remove AutoRenew__c from the schema files Category:Purchase, backend, devopsfulfillment, ~"group::purchase", sectionfulfillment, workflowready for development %14.1
• gitlab-org/customers-gitlab-com#3147 (closed) Create Annual/Quarterly True Up Products By GitLab Tier Category:Purchase, Enterprise Applications, SKU, backend, devopsfulfillment, ~"group::purchase", sectionfulfillment, workflowready for development %14.1
• gitlab-org/customers-gitlab-com#3015 (closed) Community Programs Self-Checkout - namespace-select Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development %14.1
• gitlab-org/customers-gitlab-com#3014 (closed) Community Programs Self-Checkout - subscription-details component Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.1
• gitlab-org/gitlab#327896 (closed) [Storage] Roll out feature flag ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/gitlab#327895 (closed) [Storage] Create purchase success banner ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/gitlab#327894 (closed) [Storage] Create or re-use confirm order component ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/gitlab#327893 (closed) [Storage] Create or re-use billing address component ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/gitlab#327891 (closed) [Storage] Create purchase summary component ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/gitlab#327889 (closed) [Storage] Create subscription details component ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/gitlab#327888 (closed) [Storage] Implement submit storage purchase ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/gitlab#327886 (closed) [Storage] Link to new route when feature flag is enabled. ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/gitlab#327885 (closed) [Storage] Make customer graphql client work to fetch storage plans ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development %14.2
• gitlab-org/gitlab#327884 (closed) [Storage] Create feature flag and route accepting a namespace (group) id ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/gitlab#327866 (closed) [FE] Add form validation of required customer profile form fields ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/gitlab#327859 (closed) [FE] Create a component with customer profile form fields ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development %14.3
• gitlab-org/gitlab#327858 (closed) [FE] Create a GraphQL mutation to submit customer profile details ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.3
• gitlab-org/gitlab#327857 (closed) [FE] Create a GraphQL query to fetch customer profile details ~"Accepting merge requests", Category:Purchase, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development %14.3
• gitlab-org/customers-gitlab-com#3004 (closed) [BE] GraphQL: Enable mutations in CustomersDot from GL.com through GraphQL Category:Purchase, backend, devopsfulfillment, ~"group::purchase", sectionfulfillment, workflowready for development %14.2
• gitlab-org/customers-gitlab-com#3003 (closed) [BE] Add customer profile to GraphQL Category:Purchase, backend, devopsfulfillment, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/customers-gitlab-com#3000 (closed) [BE] GraphQL: Secure gitlab.com to customers-dot proxy Category:Purchase, backend, devopsfulfillment, ~"group::purchase", sectionfulfillment, workflowready for development %14.1
• https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/2922 (confidential) ~"(confidential)" %"(confidential)"
• gitlab-org/customers-gitlab-com#2781 (closed) Remove font awesome icons and replace them with gitlab-ui SVGs Category:Purchase, Unplanned, devopsfulfillment, frontend, ~"group::purchase", missed:13.11, sectionfulfillment, ~"technical debt", workflowready for development, ~"" %14.3
• gitlab-org/gitlab#321647 (closed) [CI Minutes] Link to new CI Minutes purchase route ~"Accepting merge requests", Category:Purchase, Fulfillment Priority, OKR, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/gitlab#321645 (closed) [CI Minutes] Create a banner to display success from purchasing CI Minutes ~"Accepting merge requests", Category:Purchase, Fulfillment Priority, OKR, devopsfulfillment, frontend, ~"group::purchase", sectionfulfillment, workflowready for development, ~"" %14.2
• https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/2575 (confidential) ~"(confidential)" %"(confidential)"
• https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/2340 (confidential) ~"(confidential)" %"(confidential)"
• https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/2315 (confidential) ~"(confidential)" %"(confidential)"
• gitlab-org/customers-gitlab-com#2272 (closed) BE: Improve provisioning and onboarding of new sales-assisted GitLab.com subscribers Category:Purchase, Engineering, backend, devopsfulfillment, ~"group::purchase", linkparent issue, sectionfulfillment, workflowready for development %14.2

Group: grouputilization

• gitlab-org/gitlab#334029 (closed) Display a badge for project invite members ~"Accepting merge requests", ~"Category:Utilization", Stretch, devopsfulfillment, frontend, grouputilization, sectionfulfillment, workflowready for development %14.1
• gitlab-org/gitlab#333405 (closed) SPIKE: Filtering the Seat Usage Page - backend challenges ~"Accepting merge requests", ~"Category:Utilization", backend, devopsfulfillment, grouputilization, sectionfulfillment, spike, workflowready for development %14.2
• gitlab-org/gitlab#329937 (moved) Additional alerting of failed jobs for critical SaaS metrics ~"Accepting merge requests", ~"Category:Utilization", backend, devopsfulfillment, grouputilization, sectionfulfillment, spike, workflowready for development %14.2
• gitlab-org/gitlab#328611 (closed) Spike: Logic behind SM user counts which affect billing ~"Accepting merge requests", ~"Category:Utilization", backend, devopsfulfillment, grouputilization, missed:14.0, sectionfulfillment, spike, workflowready for development, ~"" %14.1
• gitlab-org/gitlab#328237 (closed) BE: Ask admins to confirm auto approval of pending users only when pending users risk being approved ~"Accepting merge requests", ~"Category:Utilization", backend, devopsfulfillment, ~"feature", grouputilization, sectionfulfillment, workflowready for development %14.2
• gitlab-org/customers-gitlab-com#2920 (closed) Documentation: SaaS Deprovisioning Processes ~"Category:Utilization", Stretch, Unplanned, backend, devopsfulfillment, documentation, grouputilization, missed:13.11, missed:13.12, missed:14.0, sectionfulfillment, workflowready for development, ~"" %14.2
• gitlab-org/customers-gitlab-com#2815 (closed) Follow-up from "Implement additional logging when expiring orders" ~"Category:Utilization", backend, devopsfulfillment, ~"feature", ~"feature::maintenance", grouputilization, sectionfulfillment, ~"technical debt", workflowready for development, ~"" %14.1
• gitlab-org/gitlab#323617 (closed) Connect trial flows to new trial plans ~"Accepting merge requests", ~"Category:Utilization", backend, devopsfulfillment, grouputilization, needs weight, sectionfulfillment, workflowready for development, ~"" %14.1
• gitlab-org/customers-gitlab-com#2772 (closed) Refactor Gitlab::HostedPlans::PurchasedAddOns::StorageService specs ~"Category:Utilization", backend, devopsfulfillment, ~"feature", ~"feature::maintenance", grouputilization, sectionfulfillment, ~"technical debt", workflowready for development, ~"" %14.1
• https://gitlab.com/gitlab-org/gitlab/-/issues/323117 (confidential) ~"(confidential)" %"(confidential)"
• https://gitlab.com/gitlab-org/gitlab/-/issues/329902 FE: Allow users to create a Premium trial - GitLab.com Billing Page Update ~"Accepting merge requests", ~"Category:Utilization", devopsfulfillment, frontend, grouputilization, sectionfulfillment, workflowready for development %14.2
• gitlab-org/gitlab#329900 (closed) BE: Allow users to create a Premium trial - GitLab.com Billing Page Update ~"Accepting merge requests", ~"Category:Utilization", Support Priority, backend, devopsfulfillment, grouputilization, sectionfulfillment, workflowready for development %14.2
• gitlab-org/gitlab#262876 (closed) FE: Seats Currently in Use Members List - filter members list ~"Accepting merge requests", ~"Category:Utilization", Engineering, Fulfillment Priority, devopsfulfillment, frontend, grouputilization, linkparent issue, sectionfulfillment, workflowready for development %14.3

Group: ~"group::license"

• https://gitlab.com/gitlab-org/gitlab/-/issues/334032 (confidential) ~"(confidential)" %"(confidential)"
• gitlab-org/customers-gitlab-com#3267 (closed) Add Invoice Item Charge Amount and Invoice Data and Entity to Data Packet Affects Salesforce, ~"Category:License", backend, devopsfulfillment, ~"group::license", sectionfulfillment, workflowready for development %14.1
• gitlab-org/gitlab#333585 (closed) Remove date from Seat Link data fields ~"Accepting merge requests", ~"Category:License", backend, devopsfulfillment, ~"good for new contributors", ~"group::license", sectionfulfillment, ~"technical debt", workflowready for development %14.2
• gitlab-org/gitlab#333433 (moved) Validate Customer's License File ~"Accepting merge requests", ~"Category:License", backend, customer, devopsfulfillment, ~"group::license", sectionfulfillment, workflowready for development %14.1
• gitlab-org/gitlab#333432 (closed) Validate Seat Link Request/Response ~"Accepting merge requests", ~"Category:License", backend, customer, devopsfulfillment, ~"group::license", sectionfulfillment, workflowready for development %14.1
• https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/3248 (confidential) ~"(confidential)" %"(confidential)"
• gitlab-org/customers-gitlab-com#3240 (closed) Remove report_date from LicenseSeatLink ~"Category:License", backend, devopsfulfillment, ~"feature", ~"feature::maintenance", ~"group::license", sectionfulfillment, ~"technical debt", workflowready for development %14.1
• gitlab-org/customers-gitlab-com#3220 Evaluate validation skipping and add comment with reasoning ~"Category:License", backend, devopsfulfillment, ~"group::license", sectionfulfillment, ~"technical debt", workflowready for development %14.1
• https://gitlab.com/gitlab-org/gitlab/-/issues/332492 (confidential) ~"(confidential)" %"(confidential)"
• https://gitlab.com/gitlab-org/gitlab/-/issues/332478 (confidential) ~"(confidential)" %"(confidential)"
• https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/3148 (confidential) ~"(confidential)" %"(confidential)"
• gitlab-org/customers-gitlab-com#3133 (closed) Follow-up from "Add ability to resend the activation code" ~"Category:License", backend, devopsfulfillment, ~"group::license", sectionfulfillment, workflowready for development %14.1
• gitlab-org/gitlab#329404 Activate GraphQL to distinguish internal and external errors ~"Accepting merge requests", ~"Category:License", backend, devopsfulfillment, ~"group::license", sectionfulfillment, ~"technical debt", workflowready for development %14.1
• https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/3060 (confidential) ~"(confidential)" %"(confidential)"
• https://gitlab.com/gitlab-org/gitlab/-/issues/327882 (confidential) ~"(confidential)" %"(confidential)"
• gitlab-org/customers-gitlab-com#2887 (closed) Follow-up from "Add initial params to pass to frontend" ~"Category:License", backend, devopsfulfillment, ~"group::license", sectionfulfillment, workflowready for development %14.1