Who would benefit? |
Product Managers and consumers of a Product Requirements Document. |
What impact would it make? |
It would allow for a simplified process in developing and maintaining PRDs over time, without having to duplicate efforts across the Epics and PRDs. This also ensures that the documents stay consistent and true to the information in the Epic over time. |
How should it work? |
When creating a PRD, there is a section to define Epics for a particular release. Although you can reference an Epic with the "#..." shortcut, the information in the Epic does not directly populate the fields in the PRD (or vice versa). This can result in a lack of critical information and definition in the PRD, as Epics can also have a variety of fields with useful information (Initiatives, Feature Score, T-Shirt Size, etc.). Additionally, if information is later added to an Epic after the PRD is completed, you are then required to navigate back into the PRD and copy and paste or manually enter this information. This duplication of effort can be very cumbersome, and it would be great if it can be automated. |
Thank you for your idea. There is a great option available today that should help with this use case. It is possible to embed saved views in notes. This article explains in more detail.
So you could create a view with the relevant details of all epics and embed that right into your PRD note. The view is live updated so you will always see the most relevant information.