I have my Scrumboard arranged into swimlanes. I thought (hoped) that "Base swimlanes on" - Stories would created a swimlane for each story (it does) and in this show every issue connected to that story (except epics) (it doesn't).

I qwant to arrange swimlanes by story I can see at any time the state of every issue connected to a story.
This enables me to easily see exactly what work is left to do to complete each story, and therefore what are we likely/actually going to deliver this sprint.

This helps management to maintain stakeholder expectations.

For example:

I have multiple stories in a sprint. Each story contains acceptance criteria & enough info for devs to do work. Some additional dev/qa tasks may be created and linked to the story (we don't use sub-tasks historically) with link type 'related to', or maybe even 'blocks')

Bugs for each story will be created during the sprint. These will be linked to the story (with link types being 'found while testing', or possibly, 'blocks').

I want the bugs, tasks, sub-tasks etc. related to a story to be visible in the swimlane for that story.

The ability to do this in a lightweight manner important. Having to manually set up and maintain a bunch of JQL queries (one per story) in order to get this view is laborious if we have 15 stories every sprint, and prone to error since it's a tedious manual task.

I was very happy to see Story apear in the Group By list, but disappointed that it seems to only recognise the story itself and sub-tasks as belonging to a story (and only if the story actually has sub-tasks - which ours don't). Everything else gets booted out into the big generic pile of everything else.

Currently we have to set up a query like this for each story:

issuekey= StoryID1234 or ISSUE IN linkedIssues("StoryID1234")

It would make life easier if the setting "Base swimlanes on" - Stories actually enabled this automagically.