Hello! Thank you for the video, it's certainly interesting, but I would like to ask about the specific categories that go into your bug fields. For example, in the component field I've created a dropdown menu, where you can select between: Functionality, Localization, Usability, Reliability, Performance, Supportability (yeah, that's the FLURPS framework). Alternatively, I'm thinking about adding a similar field for selecting the level of the issue: Unit, Integration, System, Acceptance. Categorizing the bugs by their testing levels, I think that could be useful at least internally for the QA team. Happy to hear your thoughts about that! Thank you.
How do you assign a bug to a specific feature ticket? I dont want a series of bugs created that are floating and disconnected from the feature ticket the dev team were working on. I can only see creating a subtask but I cant see a way of changing a subtask to a bug. I want bugs tracked with the feature that they pertain to.
Please help. I created a separate sprint with the name "Bugs", for all the bugs on the project. Now I have 1900+ bugs in it, and I have to scroll all 1900+ to the bottom to get to the backlog. Is there any way to hide them? I want to display the first 50+ bugs and the rest hidden, and have a "Show all issues" button. Does anyone know how this can be done? I hope I explained the problem clearly. Thank you all
Jira typically does compress things for you. I would recommend you also create some quick filters to show specific bugs of interest (maybe all highest priority?)
@@ApetechTechTutorials Thank you for your answer. We use filters, but it is not always effective. We wanted to separate our Backlog from bugs by creating a separate sprint (folder) called Bugs. I had that on a previous project and it was quite handy, but we didn't have the same problem there as we have here with the display. "maybe all highest priority?" No, there are bugs with different priorities from lowest to highest and they do not compress ((
To get more resources and get in contact with me check out this link linktr.ee/apetech
Great video. How do you track how many bugs the team fix or address in every quarter?
As someone with a QA background, this is a great summary. I can tell your knowledge of Jira is exhaustive due to your hardware background!
Hello! Thank you for the video, it's certainly interesting, but I would like to ask about the specific categories that go into your bug fields.
For example, in the component field I've created a dropdown menu, where you can select between: Functionality, Localization, Usability, Reliability, Performance, Supportability (yeah, that's the FLURPS framework).
Alternatively, I'm thinking about adding a similar field for selecting the level of the issue: Unit, Integration, System, Acceptance. Categorizing the bugs by their testing levels, I think that could be useful at least internally for the QA team.
Happy to hear your thoughts about that! Thank you.
How do you assign a bug to a specific feature ticket? I dont want a series of bugs created that are floating and disconnected from the feature ticket the dev team were working on. I can only see creating a subtask but I cant see a way of changing a subtask to a bug. I want bugs tracked with the feature that they pertain to.
Is there a gadget I can use on Jira dashboards to prioritize bugs?
No gadget, but it is possible for you to sort your bugs by status.
Please help.
I created a separate sprint with the name "Bugs", for all the bugs on the project. Now I have 1900+ bugs in it, and I have to scroll all 1900+ to the bottom to get to the backlog. Is there any way to hide them? I want to display the first 50+ bugs and the rest hidden, and have a "Show all issues" button.
Does anyone know how this can be done? I hope I explained the problem clearly. Thank you all
Jira typically does compress things for you. I would recommend you also create some quick filters to show specific bugs of interest (maybe all highest priority?)
@@ApetechTechTutorials Thank you for your answer.
We use filters, but it is not always effective. We wanted to separate our Backlog from bugs by creating a separate sprint (folder) called Bugs. I had that on a previous project and it was quite handy, but we didn't have the same problem there as we have here with the display.
"maybe all highest priority?"
No, there are bugs with different priorities from lowest to highest and they do not compress ((
You should give examples not just general talk ….
Agree. I should make some sort of a mock project.
@@ApetechTechTutorials would love to see that! Great video btw, thanks