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 my Community friends! For those who don't know me, I'm a product marketer on the Confluence Cloud team - nice to meet you! For those of you who do, you know that I've been all up in your Co...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs