order by rank not working as intended in next-gen projects

[John H]

We have a next-gen project with all features enabled (roadmap, backlog, sprints etc). We have created a query to enable team members to see all open items in the sprint assigned to them and we want to group sub tasks under their parent.

The standard way to do this seems to use order by rank however this does not work in a next gen project. The expect result is for sub tasks to appear under their parent (story, sub-task, subtask followed by the next story, sub-task, sub-task etc.) What actually happens is that all stories appear then all sub-tasks.

Is there a way to group subtasks by their parent in a next-gen project? here is the JQL: 

project = xyz AND assignee = currentUser() AND resolution = Unresolved order by rank ASC

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

You can control "adding worklogs" by project permissions. Is that what you mean by making worklogs readonly?

https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions

[Kate]

Not quite,

these fields should be writable in subtasks, but readonly in tasks .
Is it possible?

[Jobin Kuruvilla [Adaptavist]]

Nope, that's not possible in JIRA. If it is a global change, you can remove the worklog operation from standard tasks by adding a condition. Some modification to source files needed.