We are planning to assign up to 40 subtasks to various separate groups off of one parent issue. Is there any limit on the number of subtasks that can be created?
This is the first time we've looked at subtasks, we do not want groups to be able to view each others information. I am assuming subtasks can be locked down so that each assignee can see only their subtask's information?
This question has been answered on the related post below:
There is no such limit for number of subtasks. Having said that, It will not make sense to have a 100 subtasks on a single issue and it is more process related. You will also see performance issues if you do that when viewing issues etc.
As such, the system doesn't prevent it.
As highlighted by Jobin there, you should review whether it really is the best approach to have this many sutasks instead of a separate project, for instance.
I see this thread is almost 2 years old. Is this information still accurate? Are there performance issues when a story contains a lot of subtasks?
To keep track of something like the number of files moved from one server to another, for example, I can import file information from an xls and mass-create subtasks, one subtask per file. Then as the subtasks are closed (files are moved from server A to server B) I can report progress through something like EazyBI. I have experimented with a small number (5 files, therefore 5 subtasks) and it works well but I don't know what would happen to system performance if I created hundreds or even thousands of subtasks in one story. Any thoughts?
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot