I'm building a business process which is managed in a Jira ticket which transfers between different statues that represent the process stage.
As part of this process, I'm in need of creating sub-tasks which represent sub-processes of a specific stage, running async. The sub-tasks are notified of the result of the sub-processes and update their statuses accordingly, and the parent task will change its status according to the sub-tasks statuses.
My concern is with performance since the amount of potential sub-tasks is anywhere between 100 to 5000 sub-tasks. I made an experiment with 2000 sub-tasks and noticed a delay with displaying and updating the parent task.
Is there a recommended max amount of sub-tasks?
Will a vast amount of sub-tasks have an impact on board performance?
Is there a better way to represent async sub-processes and act on their result besides representing them with sub-tasks?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events