Hey everyone, I’ve been working with JIRA and set up a custom workflow for my project. It’s got unique transitions and statuses that fit our team’s needs. But now I’m scratching my head about something.
I’m looking at the project stats, and I see JIRA shows data for unresolved issues. Thing is, with all these custom statuses, how does JIRA figure out which issues are actually unresolved?
Does anyone know how JIRA makes this call when you’re not using the standard workflow? Is there some setting I’m missing, or does it use some kind of logic to decide?
I’d really appreciate any insights on this. It’s bugging me that I can’t figure out how JIRA is crunching these numbers with our custom setup. Thanks in advance for any help!
As someone who’s worked extensively with JIRA custom workflows, I can shed some light on this. JIRA determines open issues based on the Resolution field, not the status; if the Resolution field is empty, an issue is considered open regardless of its current state in your custom workflow.
This can be confusing when using non-standard statuses, as an issue might appear to be in a final stage while still being marked as open. To handle this, make sure your workflow sets the Resolution field when an issue is resolved, or adjust your JIRA Query Language filters to better match your process.
hey there happydancer99! i’ve dealt with this too. jira actually looks at the Resolution field to decide if an issue’s open. if it’s blank, jira thinks the issue’s still open even if ur status says otherwise.
make sure ur workflow sets Resolution when u close stuff. that should fix ur stats problem 
In my experience with JIRA custom workflows, the key to understanding unresolved issues lies in the Resolution field. JIRA considers an issue open if this field is empty, regardless of its status in your custom workflow.
To ensure accurate reporting, you’ll need to configure your workflow transitions to set the Resolution field appropriately. This might involve adding a post-function to certain transitions that populates the Resolution field.
Additionally, you can create custom JQL queries to better align with your unique workflow. This way, you can generate reports that accurately reflect your team’s definition of ‘resolved’ or ‘unresolved’ issues, overcoming any discrepancies between JIRA’s default logic and your custom setup.