I am using the Next-Gen Scrum project, I wanted to add a sub-task under a story but change its issue type from Sub-Task to a bug.
We have this requirement as we wanted to track the bugs about a story as subtasks of that story, also with this, we should be able to assign those bugs to individual developers.
If I try and add a new issue type it is not showing under the types for a sub-task.
Can't comprehend how to work with Story having this limitation in one subtask issue type. What QA team should do in case fresh implemented story has bugs? The story branch is not merged to the develop yet. This bugs is for the story only.
So they are not a project's bugs so we can't create them to the project.
@Rohan_Peshkar you can have one subtask issue type in a next-gen project and tou can rename that issue type to be what you want... https://confluence.atlassian.com/jirasoftwarecloud/set-up-issue-types-in-next-gen-projects-949233753.html
I would name it something else like Issue or Story-Bug, the need here is to have sub-tasks under a story and mark them as bugs.
@shetty the approach you suggested is not possible in Next-Gen project I suppose, while adding an issue type it is not asking whether to add as Standard Issue Type or Sub-Task Issue Type.