Hello. This software is good. Very good even. However, I have to agree that lacking this feature really makes planning a mind boggle.

It is highly important that we can create and view sub-tasks of stories/tasks in the backlog view, separately from the parent issues themselves, in order to set them into their own sprints. Some user stories require a few tasks that all together take more than a one or two week sprint. What is the verdict on this feature? Are you looking into making this possible?

+1 Not having this, or being unable to have a way to move linked tasks together, is causing a ton of overhead. Alternatively would be good to group the Kanban by sprints. Blocking this workflow + blocking all alternatives is just making the software not usable for planning.

Reminds me of the now infamous: https://jira.atlassian.com/browse/JSWCLOUD-9167

Fundamentally, Jira has made some what I'll charitably describe as "odd" architectural decisions:

They designed the ability to split Epics into Stories and allow summing of said Stories' metrics in the Epic, they designed the ability to split Stories into sub-tasks and allow summing of said Sub-tasks metrics in the Story, which would rationally imply a 3 tier hierarchy system.... but no.

They provide no pass-through ability to pull through the levels up to the parent level . There's a complete disconnect between the 2 spheres.... unless you're willing to buy expensive add-on products which only fill in some gaps. That's BAD design: you give rational, intuitive sub-divisions for people to use, and invest their time and data in, but then provide no ability to cross-reference and collate the data. What kind of rational project management paradigm is that!?

Same needs made us to come up with own JIRA add-on called Pivot Report.

You can check this demo report for Backlog here. No registration needed, just click and see it in action.

Pivot Report is available both for Cloud and Server. You can evaluate it via Atlassian  Market. 

Please fix right meow

+1 This is a must have. Reconsider this.

+1 Please reconsider this. A project basically means a group of tasks, maybe you want to create a project with only two tasks, or with 15 tasks. Is ridiculous that you can't manage this project in differents sprints.

+1 to please reconsider.
This feature would really accentuate how it is that many users including myself would like to see the subtasks shown. It is possible to work around this but to plan the sub task using time (story points) and not have either rolled up in the Backlog and Board seems to make the SubTasks useless.
Please elaborate on why they are even here if this feature isn't feasible? The option of rolling everything up a level isn't really possible in this scenario (and others' scenarios).
Please reconsider this - thank you

As noted above this is a duplicate of GHS-5797.
A separate issue GHS-7992 tracks the Suggestion for showing sub-tasks in the Backlog (plan mode).

Kind regards,
Martin
JIRA Software

Please reconsider. This is ridiculous. Your users have been asking for this feature for literally years.