We would like to have the ability to create a dependency between features. We are able to prioritize the features, but it would be useful if we could create upstream/downstream dependencies between features. This would help us understand (visualize) what block of work needs to be completed before we can start the next block of tasks.
by: Marissa F. | over a year ago | Sprint Planning
Comments
The ability to create, track, visualize direct dependencies between Portfolio Items (including Features) would be of great value! Wonderful Idea, Marissa!!
Our project also uses features for our releases. It would be very beneficial to have feature dependencies so that we can attach which features were going out for which release and know when those features are complete to start the release process.
Thank you all for your valuable input. I am happy to announce that Epic to Epic dependencies have been implemented.
Using the new Portfolio Item Dependency relationship, you can identify, capture, and manage dependencies as soon as they are identified without needing to create stories. These dependencies can be set at any level in the Portfolio Item hierarchy. Therefore, you can also create dependencies between Capabilities, Epics, Initiatives, or any level in the hierarchy. Once created, these dependencies can be viewed on the Portfolio Item Dependency Diagram and on the Portfolio Item Relationship Visualization Tab. There is also a new Portfolio Item Dependency report for those who like to see these dependencies in a tabular form.
Please check it out and keep the good ideas coming.