Skip to content

Swap Portfolio Management for Requirements Management as an example category

Justin Farris requested to merge justinfarris-master-patch-17207 into master

Why is this change being made?

While Portfolio Management does meet the category definition of "high-level capabilities that may be a standalone product at another company" it is it's own group now with sub-categories of Epics and Roadmaps. Replacing it with Requirements Management to reduce confusion.

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

Merge request reports