You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
these can be achieved but not recommended
Create sub-task issue type shown in attached image
so whenever you create these issue type under that story it will be linked as sub-task for the same. you can name it as a bug
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Agree with @shetty ,
I would never ever use the same name for a Standard Issue Type and a Sub-Task Issue Type. You will totally confuse your users with a configuration like that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.