Hello @Thays_Carvalho
If you are using default configurations for your projects and subtask issues types this is expected.
Story points should be used to estimate at the base issue level, not the subtask level. At the subtask level people more often use time in Original Estimate for estimation.
You can, however, modify the configuration to add the Story Points field to the Subtask issue types.
Hi,
The problem was caused due to migration where some fields were also migrated, I deleted the duplicate fields and the problem got fixed
*A lot of dirt goes when migrating from cloud to cloud*
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
By default, Jira Software is a Scrum tool, so it ignores issues on sub-tasks. Sub-tasks are not Scrum items, so their sprint estimates are not of any use.
You can add them if you want to, but if you do, you will need to build automations or scripts that enable them to be taken into account when you're trying to do Scrum, or you'll end up double counting them, making a nonsense of all your estimates.
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.