Burndown chart read/collect value from the story points estimation instead story points

[Tehmina Aslam]

Hi,

Is there any way to configure the burn-down chart created with the value in story points estimation rather than story points?

Or any other way to add hours estimations to the subtask and the feature issue type

[Trudy Claspill]

Are you working with a Team Managed project or a Company Managed project?

The Story Point Estimate field applies only to Team Managed projects and the Story Point field applies only to Company Managed projects.

Can you provide more context to the problem you are trying to solve?

[Tehmina Aslam]

I want it to apply to company-managed projects. As we have standard package so we can't add more hierarchies level. So we decided to use it somehow in the following way: 

Epic --> Feature --> Story/Task and Subtasks.

Subtask doesn't have story points. so if we use a story points estimation field then the burn-down chart and the other reports never work as they work with story points. 

[Trudy Claspill]

You cannot configure the charts for a Company Managed Project to track against the built-in Story Points Estimate field, as that field only applies to the Team Managed projects.

Burn down charts are not intended to track sub-tasks. Sub-tasks are not independent issues. Sub-tasks exist only as a child of another issue type. Sub-tasks stick with their parent issue with regard to Sprint associations - you can't assign Sub-tasks to a sprint independently of their parent. You should not be trying to track sub-tasks as a separate entity from the other issue types in your charts.

You can have the time estimation and tracking fields as part of your sub-tasks, and you can elect to roll-up/summarize that information to their parent issues. You can use Story Points in parallel at the Story/Task level.

The available hierarchy in Jira Standard is

Epic > Standard issue types (i.e. Story, Task, Bug) > Sub-tasks

You can add additional named issue types at the Standard level and the Sub-task level that Jira will process the same as the other issue types at those levels. If you add a new issue type named Feature at the Standard level, Jira will automatically process it in the same manner as it processes Story, Bug, and Task. Jira will not recognize a parent/child relationship between Features and Story/Bug/Task issue. You will have to artificially create that relationship using the generic Linking functionality and add other customization for other behaviors you would expect in a parent/child relationship, like rolling up story point from Story to Feature.

[Tehmina Aslam]

Thank you for clarifying @Trudy P Claspil.