create a new field at the Feature

[משה מנחם]

How can you create a new field at the Feature level that will display the number of hours spent on the project And recorded by users at story, task, subtask level?

 

[Jack Brickey]

Hi @משה מנחם , welcome to the community.

Could you indicate what platform (server, cloud, or data center) that you are using? If you were on cloud, then your URL will look something like company.atlassian.net if you do happen to be on cloud, are you on standard or premium premium allows you to have advanced Roadmaps which includes a more diverse hierarchy of tissue types that provided by standard or free tiers.

You mentioned "feature" which isn't inherently an issue type within Jira. Well, you could certainly create an issue type named feature. It will still have the same behavior has a story or task.

Regarding Your question it seems that you want to total up the number of hours associated with a body of work which in compass is a number of issues. Is that accurate? If so, the Premium tier Advanced Roadmap feature may yield what you want but likely you would want/need an addon to meet your requirements. I have use Epic sunup addon previously. the best solution would depend on your exact requirements. I would suggest looking at the Marketplace for options.

[Bhanu]

@Jack Brickey 

Epic sump is a great add-on that helps track the time spent at all levels (Epic - Story and subtask).

Script Runner can help with this if you need to calculate the total number of hours spent across all issues in project.

[Joseph Chung Yin]

@משה מנחם -

Welcome to the community.  I agreed with what @Jack Brickey suggested.  Question for you did you changed the Epic issue type to Feature issue type where story/subtasks rolls up to?

(As referenced back to 2021 - https://community.atlassian.com/t5/Jira-articles/Upcoming-Rename-epics-in-your-company-managed-projects/ba-p/1874726)

In Jira (out of the box) - parent and subtask (subtask issue type only) already have the setup to allow subtasks' story points to roll up to its parents.  However issue (non-subtask issue types) roll-up to Epic will require additional (add-ons) or customization configuration (i.e. via automation rules using Automation for Jira - https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

Once you provides additional clarification on your ask, we can offer additional suggestions.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Infrastructure Applications Team

Viasat Inc.