How do I get a bug count on the ticket front?

[Mark Nicoll]

When you look at a board with all the tickets, I want to be able to see if tickets have bugs relating to them. In Azure devops, you would see a bug count (and you can also then click this and it will list the bugs).

Is there something that can be done in Jira to at least just see how many bugs are associated with a ticket, whether it be a story ticket, epic or sub-task?

Thanks

[Walter Buggenhout · Accepted solution]

Hi @Mark Nicoll,

That is a very specific use case you are describing. I can only imagine you would be able to link bugs to stories if you have very specific procedures in place around how you define your stories as well as bugs. I don't know how you could possibly link all bugs to a specific story. Rather to an application, a functional module, a technical component or a version ...

Still, if you really want this, you could set up a workaround with automation. Create a custom field bug count and add it to your story screens. Then, create an automation rule that increases the value of that field by 1 every time a new bug is linked to a story.

That rule may look like this (just replace the impact field with bug count and the appropriate logic to update the field value: 

You can then display this custom field on the card view of your issues on the board. 

Hope this helps!

[Mark Nicoll]

Thank you for the quick reply. This looks like it is just what I am looking for. I will give it a go. Thank you

[Mark Nicoll]

@Walter Buggenhout 

I have now managed to add that automation, again thank you.

I am however struggling to find out how I add the Impact field to the project(s). I am pretty much a newcomer to Jira, so please forgive my lack of knowledge. 

[Walter Buggenhout]

Assuming that your project is company managed, navigate to Project Settings > Screens and locate the screen scheme. that is associated with your story issue type. You'll need the screen(s) that are used for editing/viewing your issue.

Click on that screen to edit its layout. You should be able to select the bug count field that you want to add (not impact, I hope 😉) and add it to your screen there.

When you get to that point, to get the field on the card view on a board, you'll still need to navigate to your board. From Board Settings, Card layout you should be able to add the field to the card view there.

[Mark Nicoll]

@Walter Buggenhout 

I am fnding that I can now see a bug field on my jira ticket, that I clicked into. I chose text field (view only) for the custom "Bug Count" field.

Is there some script or code I should be adding to this to make it work please?

The filed just says "none" when bugs are linked to the ticket (story or sub task)

The ticket: - 

I then want to show this value, once working, on the face of the ticket (example): -

[Walter Buggenhout]

Hi @Mark Nicoll , yes of course. You'll need to tell your custom field to increase its value by 1 each time a new bug gets linked.

You'll need to add this smart value to make it work:

{{#increment}}{{issue.Bug count}}{{/}}

[Mark Nicoll]

Thanks again. 

Does it only work for new bugs added from now on (since adding the script to automation), as I have tickets with bugs on them and the count is still "none". 

Also, out of curiosity, what is the code used for these mini scripts please? Just so I know for when I get adventurous and create more automation in Jira. 😁

[Walter Buggenhout]

Ah yes, obviously @Mark Nicoll. If you want to fix that for existing tickets, I would focus on the tickets currently in your board and set the counter manually. I would expect it can't be that many. Pretty soon, you should be up to date.

About the code: these are automation smart values. If you want to do any dynamic shizzle in your automation rules, they let you do all kinds of things. You can find documentation from this overview page. 

[Michał Pacewski]

Hey @Walter Buggenhout I have tried the solution - But it did not work - I tried few field type in the custom field and configured the automation as in the picture.

Is there somewhing more I should know or try?