How to expand all issues from List View

[Victoria Inman]

This morning my team-managed business project view expanded all issue types:

 

Now, it's collapsing all as I open the list view:

I haven't changed any settings. All of a sudden, it's just collapsing by epics. How can I change this back so that the default view is an expanded view?

[Jack Brickey · Accepted solution]

Hi @Victoria Inman , I have been attempting, unsuccessfully, to default to an expanded view of issues under the list view. I assume that is the view you are looking at?

[Victoria Inman]

Hi @Jack Brickey 

Yes, that's what I'm trying to do, and the view worked for me this morning and all of a sudden for no apparent reason, it has changed. Thoughts?

[John Funk]

Hi @Jane Yeoh - Did something change with being able to save the expanded view? 

[Jack Brickey]

@John Funk , how do you save expanded view. I have not found any means of doing so.

@Victoria Inman , I have never opened the list view where it was expanded. I have had to expand after opening the view. With that said I have not used the list view much.

[John Funk]

I think that's the point - you can't save the view where you left it the last time. 

[Jack Brickey]

Ok that is consistent with my findings/understanding.

[Victoria Inman]

For the last 2 weeks I've been using this list view and it's never defaulted to a collapsed view of epics. Only today did the change take place. It's not useful and I'd like it to go back. Was wondering if anyone had a solution to it.

[Jack Brickey]

Maybe contact Atlassian Support for input? I guess it is possible that a change was rolled out changing the behavior.

[Jane Yeoh]

Hi @Victoria Inman ,

Thanks for reaching out. It looks like the view you are seeing now is the nested view (Epics > Tasks > Subtasks) which we recently shipped while in your previous view, you were seeing Epics and their tasks un-nested. 

We are working on a quick expand all/collapse all capability so you can choose if your view is expanded or not. This will take a few weeks for us to implement, so we thank you for your patience while we work on this!

[John Funk]

@Jane Yeoh  - That's fantastic news! Thanks for sharing!

[Cory A]

@Jane Yeoh Is it possible that the "nested view" rollout is just making its way to me?

Yesterday (6/29/22), I could expand epics to see subtasks underneath as shown in the screenshot below, but today (6/30/22), I do not have the option to expand epics.  

[Becca Colbaugh]

@[deleted] I'm desperately trying to access this nested view on my Business project, how can I access that newly released feature?

[Becca Colbaugh]

@Jane Yeoh I'm desperately trying to access this nested view on my Business project, how can I access that newly released feature?

[Jane Yeoh]

Hi @Becca Colbaugh

We've just rolled this out to 100% so you should see this available on your list view in your business project.

[Cory A]

@Jane Yeoh 

In the list view in my business project, tasks are still nested under an epic by default.  

Based on the rollout, I was hoping to see the following:

We are working on a quick expand all/collapse all capability so you can choose if your view is expanded or not. 

I don't see a setting for expand/collapse all.  Am I missing something?

(I thought perhaps the change that you rolled out was to make the expand/collapse view sticky on a per user basis, or at least make that session-sticky, but that's not the case either.)

Thank you!

[Becca Colbaugh]

@Jane Yeoh - that's fantastic news. I tried logging out and back in, and unfortunately, I'm still not seeing existing deliverables (stories) nesting under existing projects (epics).

From list view, I can create deliverables under epics which then automatically nests. But I would expect issues I create from the epic ticket would still nest under Project View. What's the best way to talk with someone about this specific issue with my account? 

[Neshe Sabedini]

We are having same problem. I am creating Epic, Task, Subtask, but when you click on Epic, you cannot see task under Epic. 

[STOCKER Benjamin]

We have exactly the same problem. As soon as you want to unfold an Epic by clicking on the unfold button, nothing happens.  The unfold icon changes the status, but that's it. Without this function, the list view is pretty useless. 

[Kathryn O_Neill]

@[deleted] is there an update or can you assist with this issue. The thread above has answer accepted but this is still an ongoing issue. I have emailed you twice with details and screen shot of nesting issue for Epic>task on the business project list view.

Thank you

[Yuji Sakai]

I created a feature request to make the timeline/list views expanded by default:

Ability to expand all child issues in Timeline and List views by default 

• Make sure to give your vote on the request to increase the chances of this being implemented on future releases.
• Also, feel free to add any comments there, so the product team can be aware of your need for this functionality.

[John Funk]

Thanks, Yuji! I have voted for it. 

[Keith Johnson]

Has this been resolved since the last comment was made on 10/10/22?

I hope I am understanding the need here to make sure it is the same need I have. From the portal where the customer's enter their tickets and then review those tickets, this is where I need it to show an expanded view of all the comments.

Thanks

[Jack Brickey]

hi @Keith Johnson , this post is not about the Portal view in JSM. This is about the List view in JWM.

[Jason Baumgart]

My current state on this issue.

For context, not everyone may want the same configuration design being suggested, expanded as default, not expanded as default.  The idea is to make it so each can set their defaults individually.  This would be a configuration settings request, where we have the ability to set our own default views and behavior.  

For reference, What I've noticed as of today (in my case), is that if you create issues from the board or cards view and then navigate to the list view, you'll see the full list un-collapsed displaying every issue created.  However, if you create your highest-level issue from either the board or list view, then from the list view, click on the add child issue, it will establish the ability to expand and collapse only those issues created using this method.  Other issues not created using this method will appear as though they are not children of a parent issue, even though they may be and only viewable from the card view.

Hope this helps when creating your projects in the understand of how the current functionality works.

Suggestion here would be for Atlassian to fix, what is understood as an issue, where linking children's issues is conditionally honored depending on which view one is observing, either from the board view or list view and for where the child issue was initially created in the different views.  *When creating issues and child issues from the board/card view the list view does not honor the issue hierarchy when attempting to expand or collapse.  In the list view the child hierarchy is only honored (in my case), when the child issue is created from the list view.