Hello @Raju PSR
Welcome to the community!!
Using the native functionality, custom issue types (Feature, in this case) can be created. These issue types can then be used in a hierarchy as per the use case.
As Story is a default issue type in Jira, this hierarchy would need to be maintained manually. Else, you can create another custom issue type of sub-task category and name it like 'User Story'.
Please accept the answer if this helps.
Thank for for the response.
Can you give more details how to do it manually?
When I am creating the story can I select the field for value feature ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Raju PSR
You can either define a new relationship or use a custom field to store the value of the Features in the Story.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That seems like a lot of work. Because we have Advanced Roadmaps, we created an issue type called Initiative and used the Epic as the Feature.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's called Parent Link. That ties it to the Initiative, for us.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Raju PSR
You can use issue links to create your own hierarchy above and below Epics.
To visualize the hierarchy based on the issue links, we have created an app to track the progress at each level,
Agile Tools - Epic Tree, Links Tree and Time in Status
Key features of Links Hierarchy:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.