Understanding Child Work Item Limits in Jira Align

Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Is there a hard limit on the number of child issues that can exist on an object in Jira Align?

Environment

Jira Align

Solution

In Jira Align, there is no documented hard limit on the number of child work items that can be associated with a parent object. However, it is important to consider best practices to ensure optimal performance and usability.

Key Points:

  1. No Documented Limit:

    • Unlike Jira Software, which has a known limit of 500 child issues for certain operations, Jira Align does not have a specified hard limit. However, maintaining a manageable number of child issues is advisable.

  2. Performance Considerations:

    • To ensure the system performs optimally and remains user-friendly, it's recommended to keep the number of child issues at a manageable level.

      • This helps teams manage and navigate their work across Jira Software and Jira Align.

  3. Best Practices:

    • If you anticipate needing to manage a large number of child issues, consider breaking them down into more manageable groups.

    • Refine your hierarchy to support your workflow better and enhance system performance.

  4. Aligning with Jira Software:

    • While Jira Align operates differently from Jira Software, aligning the number of child issues with Jira's limit of 500 can help maintain consistency and performance across both platforms.

Updated on April 14, 2025

Still need help?

The Atlassian Community is here for you.