How to designate "Build" issue type to get various approvals required for "releasing" on production

priyanka pore
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 20, 2022

I am trying to use "Build" issue to seek approvals required from various teams and approvers for releasing a verion into production.

Issue i am facing, Build is designated as "Task" so it only allows to create sub-tasks under it which other teams are not willing to consider as 1)do not add to velocity in Story points 2) will have to chnage board filters to reflect sub-tasks, which will show subtasks for all stories and tasks.

Is there a better way to do it? Is there a possibility that we can deisgnate "Build" as Epic so all child tasks can be "tasks" instead of "sub-tasks"?

Thank you!

1 answer

0 votes
Craig Nodwell
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 20, 2022

Hi @priyanka pore welcome to the community.
Epics/Stories/Tasks are all standard issue types.
Epics get special attention in the system via issue links and system fields.
You can emulate the Epics behavior in the same fashion through the creation of some smart custom fields to follow the pattern of the EpicLink/EpicName and setting up your own issue linking.

Have a read on issue links.
 

Suggest an answer

Log in or Sign up to answer