Does anyone know how to make an epic's parent issues visible in the epic? This morning any epic with +100 issues are no longer visible - this is putting major strain on large projects.
The epic now shows that children are not visible but we do not use children issues only parent
Here is the copy that shows where the issues were visible last week:
The issue view can only display up to 100 child issues. You can still add and bulk edit them from here, but you'll have to view them in search and won't be able to include them in time tracking. Learn more about child issues"
I agree with all of you above. We are quite a big company struggling with this. It is super frustrating.
This change is incredibly frustrating and I am in shock that JIRA PMs allowed this to simply happen. Please please please please revert this change dear JIRA gods
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here. This problem is extremely frustrating and has been a huge impact on the way we use Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Agreed - this is a major area that many of our team go to review the child items of epics. Many on my team are pretty upset about this change.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Honestly can't believe they just went ahead and disabled that. That's removing a major functionality out of the blue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
They probably removed this due to the load the child issues rendering was imposing on their infrastructure. Anyway, removing this without even allowing you to override it is a pain in the ass.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This change is just beyond frustrating. This tool just lost its functionality and value for our teams, while prior to the Epic/Issues change we've been using Jira on a daily basis.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
During the past week we really tried to deal with the change, but it's a big struggle. The entire team (more than 80 people) is frustrated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you would be interested in a marketplace app to get the Epic hierarchy on your issue screen, you can try out our add-on
Agile Tools - Epic Tree, Links Tree and Time in Status
Key features :
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I got an answer on my similar post: https://community.atlassian.com/t5/Jira-questions/Can-we-disable-View-child-issues-in-search/qaq-p/1971370?utm_source=atlcomm&utm_medium=email&utm_campaign=mentions_answer&utm_content=topic
It might solve the problem but it is quite expensive
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Joshua P @Cassie Utt @gal.almog @Anna Taibishlak @Nir Liran JIRA has answered my Internal Support ticket with the following:
"This situation is already tracked on the following Improvement request and gathering interested customers and I made sure to add your case internally to it:
https://jira.atlassian.com/browse/JRACLOUD-78677
I highly encourage you to add yourself as a watcher to follow-up on its progress and provide any feedback you might have on the comment section (make sure you're logged in to the system). This helps us in understanding the impact that it might be causing to you and other customers. On top of that, it creates a path of communication between all impacted customers with our developers and product managers.
Can you and your team vote for this issue so we can get priority?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This issue was marked as closed, however this was identified today while I was working on report.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.