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.
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.
@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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There's not a lot else you can do - Jira is an issue tracker, with sub-tasks intended to split tasks up into more manageable bits. 500 bits is far too many for humans to process as sub-tasks, they would, and should put them into projects, so it's not designed for huge numbers of sub-tasks on single issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I understand the creation of 500+ subtasks is not ideal but this decision was taken on a small dataset. Right now since its scaling, we are addressing these issues.
Thanks. I would then move all the subtasks to a separate issue type and link them to the original task as a separate issue link.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think it is scaling - when you've got more than a couple of dozen subtasks, it gets too messy for humans.
I think you've got the right idea with your moves though.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.