nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

>500 Subtasks per issue

keval.doshi

Hello everyone,

I have built a system in JIRA wherein my tasks would have >500 subtasks each. I am concerned about all of these causing a slow load on the UI page for the Parent Task.

I have explored options to

a. Hide all subtasks

b. Paginate the subtasks

c. Only display the subtasks that I need (probably through a jql)

I haven't been able to find a solution to this yet. I believe this would trouble me going further if not solved now.

I have an option to move these subtasks to a different issuetype now (This would be the last resort)

Would having such a high no. of subtasks be a problem? Please suggest a good way to handle this case.

Accepted answers

All comments

Nic Brough -Adaptavist-

500 subtasks is not an "issue", it's a project in its own right. You should create a project for this "issue", and have 500 tasks within it.

keval.doshi

@Nic Brough -Adaptavist- I have a created a project P1 which have issues I1, I2, I3, etc. Each of these issues can have >500 subtasks.

Nic Brough -Adaptavist-

You said that already.

What you need to do is move up a level. If an issue is looking to have 500 sub-tasks, it's not an issue, it's a project in its own right.

keval.doshi

Thanks for the suggestion.

But I am maintaining an inventory system here which would result in such excessive number of subtasks. I would prefer keeping them under the same project.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

sub-task