Jira Categorisations

Question

Hi community.  Jira has the list of categorisations below, each can be associated with an issue in Jira.  So each issue is categorised in some way with the below.  What I would like to do is, take an export from Jair, of open issues for a given project, to enable me to capture those issues that require collaboration between the business functions and programme team to be able to resolve/deliver/complete/close (call it what you will) the issues.  But, if I generate a report, to enable the CSV export, based on all the categorisations below for the open issues for a given project, I get thousands of issues in the report.  That being the context, are some of the categorisations below, purely programme/devops business (i.e. issue to be resolved by the programme team only that do not need collaboration with the business functions)?  If somebody out there has a view, as to which of the below categorisations will need collaboration between the programme/business to resolve/deliver/complete/close issues, I would be grateful for your input)?  Thank you.  The categorisations are:

Bug

Build Up Task

Burndown Task

Epic (process)

Escalation

Feature Change

Integration

Module (parent of process)

Observation

Pre-Condition

Report

Request

Requirement

Stuart Wilde · Answer

Thanks Nic/Trudy.  I am new to Jira; these categorisations are not mine and they are being used by the Hera Project.  The categorisations have been agreed some time ago (I guess) to assist Hera but you raise good points.  I suspect, any of these categorisations could generate collaboration between the business and programme teams to resolve the issues - but thanks for your inputs and the good points you have raised.

Trudy P Claspill · Answer

And which field in the issues displays the values that you listed?

Nic Brough -Adaptavist- · Answer

My first instinct was to suggest that these categories are issue types, but actually, they don't look like that.  They don't even look like a way of categorising issues distinctively as any issue could be none, one, or many of these things.  For example, an issue raised by an end-user could be a request (because they raise it in the service desk), a bug (because they're talking about a bug in the code), a report (because the code is supposed to be providing a report), a burn-down because developer work on fixing it burns-down, a burn-up because any issue that burns-down also burns-up, maybe a feature change too if the bug is actually "report is wrong", an escalation because it doesn't get fixed fast enough, and and and.

I think we should take a step back here and ask what problem your categorisations are trying to solve?  What reporting are you actually looking for?