The development team has planned the sprint and broken down an epic into tasks and subtasks. Project Manager, Amy, wants to track the number of subtasks within the epic to better manage workload distribution and task progress. Amy requested the creation of a Dynamic Custom Field that automatically counts all subtasks within an epic. Admin configured the custom field using a Jira Expression to ensure the subtask count is dynamically updated without manual input.

Once the epic is planned, Amy opens the epic in Jira and immediately sees the "Total Subtasks" field displaying "5" This clear, automatic calculation allows Amy and the team to quickly understand the overall breakdown of work within the epic.

As more subtasks are created or completed during the sprint, the field updates automatically to reflect the latest count, giving the team a reliable way to track and manage task complexity. By implementing this dynamic custom field, the team benefits from improved visibility and automation, ensuring they always have an up-to-date view of the total subtasks in each epic.

Agent Phill got a ticket CUS-189 to resolve. He needs to assess its complexity first to know how to approach it. Dynamic field custom fields that count external and internal comments are added in this project screen, so after opening the ticket, he sees that there are 6 externals, and 2 internal comments. Also, the team uses Dynamic field to count attachments and linked issues, so Phill also sees the number of them. Having those numbers, Phill right away knows, that this incident is bigger and it can be global. Hen can immediately judge by the linked issues that it is not a single incident and is more complex, occurring among multiple reporters. It surely can take longer, so Phill can plan more hours to deal with it.