I’ve set up a custom workflow in JIRA with my own transitions and issue statuses. Now I’m wondering how JIRA figures out which issues are still open when it shows project stats. Does it use some built-in logic or do I need to mark certain statuses as ‘unresolved’ somehow? I’m not sure if my custom setup affects how JIRA counts open issues. Any insights on this would be really helpful. I want to make sure our project stats are accurate and reflect the true state of our issues.
In my experience with custom JIRA workflows, the ‘open’ status isn’t automatically determined. You need to explicitly mark statuses as ‘unresolved’ in your workflow configuration. This is done in the workflow settings, where you can flag specific statuses as ‘unresolved’. JIRA then uses this to calculate open issues for project stats.
It’s crucial to review your custom statuses and ensure they’re correctly marked. Otherwise, your project metrics could be off. I’ve seen teams get confused when their custom ‘In Progress’ or ‘Under Review’ statuses weren’t counting as open issues.
Remember, JIRA’s built-in logic only goes so far with custom workflows. It’s on us to define what ‘open’ means in our specific project context.
i had similar issues with custom workflows. u need to manually mark statuses as unresolved so jiras stats count them correctly.
i know it’s a pain, but check your workflow config to set it up right.
Having dealt with custom JIRA workflows for several years, I can tell you it’s not always straightforward. In my experience, JIRA doesn’t automatically categorize issues as ‘open’ in custom workflows. You need to explicitly define which statuses should be considered unresolved.
This is done in the workflow configuration section. There’s usually a checkbox or option to mark a status as ‘unresolved’. Once you’ve done this, JIRA will use these settings to accurately calculate open issues in your project stats.
One gotcha I’ve encountered is forgetting to mark transitional statuses like ‘In Review’ or ‘Waiting for Approval’ as unresolved. This can lead to misleading metrics if you’re not careful. It’s worth double-checking all your custom statuses to ensure they’re categorized correctly.
Remember, JIRA’s flexibility is both a blessing and a curse. It allows for highly tailored workflows, but requires careful configuration to maintain accurate reporting.