Once a feature has been released, I would like to move the requirement page to a subpath or somewhere that I can access for historical means, but keep the left menu and product requirements list uncluttered by only showing current and future requirements. It would be nice to have this automated after the linked release is done, but for now a method of manually moving them would suffice.
I tried to copy the existing Product Requirements page to 'Archived Product Requirements' and use additional label of 'released' but this did not work as the labels are not an AND match, it seems they are an 'OR'. So all requirements pages show up in the list on both container pages.
How have others managed clutter over the lifecycle of a product?
Hi Richard, I read some answers about the same question you have, and I found an add-on that does it.
Archiving - other than that I would suggest labels but you already tried.
Hope it helps.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.