I'm trying to find the proper way to collect bugs/issues in Jira's next-gen projects. Looks like this feature has been requested by many users.
How other PM's are dealing with skin bugs in this case?
You can do that with issue types. Read more here on set up issue types in next-gen projects. By default, next-gen software projects come with the bug standard issue type which is used...
... to track problems with software, such as user interface discrepancies, broken functionality, or other niggles experience by users.
To add bug issue types:
If you're going to have many bugs and it's unlikely to do them all in a given Sprint, you might want to enable backlog because that way you won't have them all in your team’s board. To enable or disable the backlog:
Hi @Wasaqat , welcome to the community. First you indicate you’re interested in next-GEN projects which by the way has been renamed to team managed projects (TMP). However, you are showing a tag of being on server which doesn’t support TMP. Are you on server or cloud? If Server then TMP will not be supported there as Atlassian is EOL-ing server.
finally, what do you mean by “collect” bugs and issues? Regardless of platform or project template used Jira fundamentally about creating and tracking issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In his las sentence here Jack is using the word "issue" to describe the various types of item Jira tracks.
If those items happen to be bugs or issues, that's fine, Jira was built in 2002 to track bugs and issues, and still does in team-managed (next-gen) projects, so the question is "what makes you think it does not 'collect' bugs and issues"?
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.