[Advanced Roadmaps] Custom Status issues not shown on a Plan

[Gonzalo Perez Alonso]

Hi,

I have a Plan with the following JQL filter: 

issuetype not in (Task, "Test Case") AND labels = CbFC_project_2025 ORDER BY status DESC, issuetype ASC, created ASC, key DESC

My problem is that a bunch of issues that are on a specific custom status (Deploy to Prod) are not being shown.

Any clue on what's going on here?

Thanks in advance.

--

Here's what I've already checked in case it might be helpful:

1. Status Category Not Included in Plan's Scope - The status "Deploy to Prod" is green (Done category) Some other issues that are in other statuses with "Done" category are being shown.

2. Exclusion Rules - no issue types/statuses are being used as exclusion rules for this plan. The timeframe for the completed issues is 360 days (the affected issues should be contained)

3. Issue Sources and Plan Filters - No filters are being applied. Regarding issue sources, the only criteria applied on the configuration is: filter by project = project name.

4. Issue Permissions - I see the affected issues when searching using the JQL, so not the case.

[Gonzalo Perez Alonso · Accepted solution]

After some trial/error I've found the root cause.

Apparently, when any issue transitions to a green status (Done category) without any of the target dates populated (target start & target end), the issue disappears. 

To avoid this from happening, there are 2 possible solutions:

• Populate at least one of these 2 fields related with dates before transitionning.
• Change the status category from "Done" to any other category.

Just wanted to share it in case someone finds this helpful.

Regards.

[Trudy Claspill]

Hello @Gonzalo Perez Alonso 

Are the issues in the "Deploy to Prod" status of an issue type other than Task and Test Case? Do the issues in the "Deploy to Prod" status have the specified label (CbFC_project_2025) assigned to them?

[Gonzalo Perez Alonso]

Hi @Trudy Claspill

These issues are user stories and have the proper label associated. Take into account that, when I use the same JQL on the issue explorer, Jira returns these issues.