RELATED IDEAS
Enable reporting & timeline dependencies from feature based on a work request
Who would benefit? |
Product Managers managing work in multiple workspaces with multiple teams |
What impact would it make? |
Enable teams to report out on timeline impacts for the feature/epic relationship as it crosses workspaces |
How should it work? |
Allow report writers to pull the timeline based on the work request into the self built roadmap report, and add a flag that enables the epic to have the timeline adjusted based on the dependency of the features similar to if the feature was in the "main" workspace |
Yes, like the below (it says feature yet it's an epic as Nike changed our language for Aha!). This is for team epics in our workspace so it's much easier, yet it would allow us to know when a epics children are part of our timeline or not. Because the feature is calculated based on the team epics (in the workspace) we can see the timeline for this feature (epic). Ideally we'd see the same thing in our roadmap view when a epic child is in a different workspace informing us of our new timeline dates without having to manually compare notes.
Steven
Thanks for sharing this idea. I have a clarifying question to help make sure we really understand your request.
Here's how I understand your idea:
Reporting setting that allows you to visualize an epic's start/end date based on the start/end dates of the epic's children and dependent records
Is this correct?