Who would benefit? |
Customers who are required to share feature documentation with enterprise or large government clients |
What impact would it make? |
Ease of hiding internal information or displaying only customer relevant information |
How should it work? |
An inheritance based configuration of what fields to include when exporting a feature/epic to pdf/png For example, the current export to PDF includes Ideas, Perspectives, Linked Records as well as all custom fields. Being able to hide some of those when needing to share features externally would allow for cleaner exports. Sometimes we'll have links to other customers features so that we can think about a broad configurable solution, but at the enterprise level (or large government entities like States), they do not want to be in "competition" with your other customers. Per contract, we share our feature designs for customizations with our large customers. It takes work arounds to show what is relevant to that customer instead of having a nice smooth export to pdf process that is build in but not configurable. |