Having the visualize per item (for example in a initiative) is great. But what would help us even more would be the possibility to have a product line wide visualization so we can how all different initiatives depend on each other.
Cristian Santayana
over 4 years ago
in Dependencies / Reports
0
Future consideration
Dependencies in to-dos / Related to-dos / disabled to-dos based on conditions
We want to create a list of to-dos where each to-do only would being active after previous to-do is marked as completed by all assigned people. That would allow to create multiple to-dos at once without irritating people by assigning to-dos they c...
Guest
almost 3 years ago
in Dependencies / To-dos
0
Future consideration
I would like the ability to have the dependency icon stay visible or pin it if there is something in that field, (if there are no records, the field should not show) versus having to hover looking for it. Additionally, currently when I hove it it'...
Fatimah Gorin
over 3 years ago
in Dependencies / Roadmaps
0
Future consideration
Dependency Report - Provide columns on Primary record instead of concatenating the fields together
On the dependency report - we often want to put the AHA feature ref ID; the name of the feature and add a tag. Providing more than one piece of information to make it useful to the user as they view the dependencies to the related records that can...
Robyn Ballard
over 3 years ago
in Dependencies / Reports
0
Future consideration
When we are dependent on say another feature, if that feature's date changes, I never know about it unless I check on the status. I know I can add myself as a watcher but would get updates on everything and I'm really only interested if the due da...
Allow the screen to scroll when setting a dependency
When I have a multi-line gantt chart with lines below the edge of my monitor, the screen will not scroll down to allow me to drag a dependency from the top of the chart to an object at the bottom of the chart.
Keep history of record links being added and removed
What is the challenge? Today there is no history of linking between records. So if a record was linked it's not recorded in both records history. Further if someone removed a link there is no trail either. What is the impact? We use linking to con...
Becky Amirault
3 months ago
in Dependencies
0
Future consideration
Allow Portfolio Initiatives that use 'Work Requests' in other products that are accepted as ideas, which are then promoted to initiatives in the product to have the ability to automatically connect back with a 'dependency of' relationship to the Portfolio Initiative
What is the challenge? Use Case/Scenario: We have a business problem where Aha Products are receiving both Ideas and Work requests and need to prioritize the potential resulting work effort. Business Problem we are trying to solve: When a Aha Prod...
Mike Jacobson
4 months ago
in Dependencies
0
Future consideration
Ability to add comments to the link records or the reason for dependency.
What is the challenge? Not able to comment to why a particular linked components are dependent of other one. What is the impact? For certain dependency to be created there are some additional comments required hence we are looking for a comment to...
Be able to remove the 'Epic' record selection from the dependency report configuration even though they may be disabled in the related workspace.
My client is using the the 'Initiative' record type as their 'Epics' in order to also be able to use the bidirectional integration with Azure DevOps. Because of this constraint, we needed to erase the 'Epic' record type from view as to not confuse...