Hello @adrian.waters ,
First, from your screenshot it looks like all the issues are in the same plan as I can see EMP and CORE issues listed but also make sue the other issues are not being excluded from the plan, as covered in the "Dependencies report" documentation:
This report allows you to see a list of all the issues, which have a dependent relationship between them within the same plan
Also covered in the same document has the plan been calculated since the dependencies were added?
All issues that appear on the dependency report are based on calculation. If you don't see all the issues you would expect to see, make sure your plan is up to date.
Next if the above options do not yield any change, check out the following thread, where other users noted running into a similar issue and were able to fix the issue by "removing and re-adding the Dependency link type in Portfolio Dependency settings":
As noted in the thread the issue that they were encountering was this Bug, but that particular bug was already fixed so something else is occuring here but looks like a similar outcome in the behavior.
Before you try removing and re-adding the values to see if it corrects the issue can you also check the browsers dev-tools settings in the javascript console output to see if there are any errors while viewing the page that might indicate the error that is occuring and let me know if you find anything.
Regards,
Earl
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.