Measuring "completeness" of a Story when using Tasks or sub-tasks

[Deleted user]

Looking for ideas on how to measure how complete a Story is when using either Tasks or sub-tasks as the underlying structure level. Either Epic -> Story -> Task or Epic -> Story -> sub-task. For example if there are 10 tasks/sub-tasks and 6 are Closed how to show that the Story is 60% complete? This can be either at the issue level with a field or using some type of report.

I know in Jira that Stories and Tasks sit at the same level, to have the 1st structure I would need to have some type of link to put the Task under the Story. This post is not to debate which structure is best, there are several other posts that do that.

The goal is to use Story Points on the Story but they can't reflect the progress of the Story and only show on Burndown charts when the Story is closed. I know I could use sub-tasks with time - Original Estimate/Remaining, log work against the sub-task then roll it all up to the Story but we are trying to stay away from using time in estimating and logging.

I would prefer to do this with no plugins however I realize I may not have a choice, if that is your suggestion recommend one if necessary. 

[Bill Sheboy]

Hi @[deleted] 

You could do what you are asking with custom fields and the automation rules, which are included with the Cloud version.  Please look over these links to learn more information:

https://www.atlassian.com/software/jira/guides/expand-jira/automation

https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/

Note that for project-level rules, the number of executions is unlimited.  But if you are doing this for global (instance-level) rules, there is a limit on the number of executions unless you spend more on licensing.

Best regards,

Bill

[Deleted user]

@Bill Sheboy thanks for the info, been thinking about this quite a bit since July. Only concern with the automation is having to do it and maintain it on several projects.

We are talking about using Eazybi plugin as we have identified other areas which that plugin will address as well.

[Bill Sheboy]

Hi @[deleted] 

Thanks for the follow-up information.  I completely understand the maintenance issue.  Depending on the complexity of your definition of completeness, you may be able to create generic rules that your site admin just copies to projects.  That could lower the effort costs.

If you frequently change your definition of completeness, decentralizing to allow the teams to do this with rules or an add-on could help more.

Best regards,

Bill