I read somewhere in the forum, one of the blockers for a kanban board showing story subtasks is the RANK ASC, I've done that and no luck.
project = "Jersey EPR" AND "Epic Link" = JE-17 ORDER BY Rank ASC
Would welcome any advice to resolve
Not sure what you're reading about the ordering, as that is not the problem in the slightest.
The problem is that sub-tasks do not have an Epic Link (much as I'm an Atlassian fan, this is absolutley one that they've got totally wrong). The Epic a sub-task belongs to is that of its parent issue (it has to be, a sub-task is but a part of the parent issue).
But Atlassian don't expose that in the search, and it's very annoying because it breaks perfectly valid searches like yours.
I don't think there's a way to fix this on Cloud, unless you set up a script or automation that copies the Epic link into another field that you can put on issues at every level.
Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event