The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions
Release Notes
Community
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

I'm trying to use the dependecies report, but it is not showing our issues with dependenccies

Steve Harris
Steve Harris
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Get involved
March 21, 2018

We've checked and ensured that indeed we do have active dependent issues, but none of them are showing on the report.

Any troubleshooting advice would be helpful.

 

Watch
Like Be the first to like this
1154 views

1 comment

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

shafqat
shafqat
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 27, 2018

Hi Steve,

New dependencies may not appear until the plan is calculated. Could you try re-calculating your plan and see if it causes your dependency to appear?

If you're running Jira in Server, there was a bug causing issues to not appear that's been fixed in 2.11.0: https://jira.atlassian.com/browse/JPOSERVER-2069. So upgrading Portfolio could fix the problem.

If that doesn't help, could you raise a support ticket for us to investigate this further: https://support.atlassian.com/contact/

Thanks,

The Portfolio for Jira team

Like
Reply
groups-icon
Advanced Planning in Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Release Notes
    Copyright © 2026 Atlassian
    Privacy Policy Notice at Collection Terms Security