Jira next-gen board display of subtasks almost useless. Anyway to configure it?

Question

With next-gen jira, I don't understand the design choice to display the board view grouped with subtasks the way Atlassian has chosen to do it. The display is that each task is displayed with its subtasks below it in their lane; then the next and so on. Tasks without subtasks are displayed below all those that have subtasks on the board.

It seems to me that displaying subtasks on the board via a checkbox as in classic and having them appear alongside every other card to then be moved around made a lot of sense.

This new display mode calls for an almost impossible amount of verticle scrolling leading to it being impossible to get a complete and clear view of the entire board.

Larry_lef52k · Answer

"I am trying to to show subtasks of a next-gen project in the board of a classic-gen project, which is configured as a cross-projects boards including multiple projects (since next-gen cannot do this). Turns out: subtasks do not show up at all. Cannot find any configuration cause."

It's sad that I actually understood this. It's even sadder that it still didn't work. Sadder yet that you've (we all have) invested so much time learning the system that you're able to do that and these guys at Atlassian don't get that about their customers.

Richard Kiefer_v2meyy · Answer

I agree. It is badly designed. It was just fine, from a user perspective, in the classic-projects. I understand that Atlassian has to deal with a lot of legacy code and this is hard. I know this from working with legacy code myself. Atlassian took the approach to side-develop entirely new code, called the next-gen projects, with a different architecture. But the feature-loss this new implementation has provoked over the last years is just hilarious. Basic classic-project stuff is not present anymore in the next-gen, and the next-gen stuff works nice in some places, but definately not for someone who wanted a solution for their classic-project problems. Now, they just have different problems.

For me, Atlassian Jira product development might work as a warning: do not make side developments, where you leave your legacy stuff broken, your new stuff full of feature-loss, the bridge between new and old rather incompatible, and then take years to transition fully. Sorry, this plainly cannot be a good way to go, speaking as a customer using Jira and experiencing the results of those development decisions.

Well, enough ranting. In essence, I have the same problem as you, but I am trying to to show subtasks of a next-gen project in the board of a classic-gen project, which is configured as a cross-projects boards including multiple projects (since next-gen cannot do this). Turns out: subtasks do not show up at all. Cannot find any configuration cause. So I guess it is due to the next-gen nature. ... unbelievable.