All Issues In Filter vs All Top Level Issues

Agile Docs lets you select a top level issue type to pair with your filter. If you’re using an issue hierarchy which has Epics at the top level, you might choose to select Epic as your top level issue type.

On this setting Agile Docs will load all Epics in your filter at the top level, then load all children of those Epics underneath and so on.

But what if you want to show multiple issue types at the top level? You have a couple of options.

All Top Level Issues

Loads all issues which have no parent at the top level. On this setting, Agile Docs will only load issues in your filter at the top level if they have no parent and are unlikely to also be displayed elsewhere.

For example, if a Story in your filter has a parent Epic, it will not be loaded at the top level. It will only be loaded under it’s parent Epic.

Use this setting if you want to show a tree of all issues in your filter but want to exclude issues at the top level which may also be loaded under their parent issue.

All Issues In Filter

Loads all issues in your filter at the top level regardless of whether they have a parent or not.

If a Story in your filter has a parent Epic, and that Epic is also in your filter, both the Story and the Epic will be loaded at the top level.

This means the Story will be loaded at the top level AND as a child of the Epic. This may not be what you want.

If you only want to show the Story under it’s parent Epic and not at the top level, you should use All Top Level Issues.