MISSING issues in Filtered Fix Version View in Portfolio for Jira??

[Tori Larsen]

Hi,

I really am stuck and hoping to get some help.

We have several issues tagged to the same fix version. All of them are tagged to a close status. The Plan is using an entire Project. Thus all the issues are pulling into the plan correctly.

However, when I use the Releases Report, and filter by Fix Version, only 2 of 6 are showing up. All 6 are tagged to the right Fix Version (I triple checked). Thus, I do not understand why 4 are just missing in this view?

Thank you!

[Earl McCutcheon]

Hi Tori,

On the surface the only thing I could think of is that there is another plan filter in play, and possibly the Scheduled range conflicting with Target dates or the Completion date is set for current sprint and the issues were completed previously

Select the "More drop down >> Scheduled range" and "More >> Completion Date" to display the filters settings, and check if there are date ranges set for the filter that would cause a conflict with the dates on the issues.

Regards,
Earl

[Tori Larsen]

Hi Earl!

Thank so much for the response.

Unfortunately, I just confirmed that the Completion Date correctly accounts for the time period. Yet the issue is still not pulling in. Meaning, I used a custom completion date of "Since 1/1/19", and the missing issue was closed in February,

Thus, I am really at a loss for how to get these issues to pull in.

All the best,

Tori Larsen

[Earl McCutcheon]

Hi Tori,

Thanks for the confirmation, and I've been playing around with this a bit to try and replicate but so far I have not ben able to get issues to show up in scope but not the report.

I wan't to get a few points clarified to better understand the scenario. 

First, is it possibly the Hierarchy level for the missing issue types?  Exe, if you have 2 Epics with 4 stories, and you are viewing the Scope at the Epic Hierarchy you can expand the Epic to see the stories in the scope details, but when viewing the release report, only the currently selected hierarchy is displayed, so only the two Epics would be shown in the report,  if you change the hierarchy to a different level do the other issues get displayed? EXE:

     VS.     

Then if thats not the case what's your jira version and portfolio version so I can verify its not a problem specific to the versions of the applications.

Next you noted:

"when I use the Releases Report, and filter by Fix Version, only 2 of 6 are showing up. All 6 are tagged to the right Fix Version"

Do all 6 show up in that release report for that version when you do not have the releases filter set or are there only two issues displayed in the version when all the releases are displayed?  EXE:

    VS.   

Regards,
Earl

[Tori Larsen]

Thanks so much for the quick response!

I am only using the Story layer of the hierarchy so that would not be the answer.

In terms of the versions we are using, 2.17.1 for Portfolio, 7.6.9 for jira version, and 7.6.0 for jira agile version.

The second picture is from the Kanban Board that shows the card views of sample issues not pulling in, while the third picture shows the Release Report view in Portfolio with the Fix Version that should contain those missing issues.

The first picture shows the Scope view without any filter in Portfolio, which you can see is pulling in one of the sample issues.

Thank you so much for your help!

[Tori Larsen]

Third picture:

[Earl McCutcheon]

Hi Tori,

Thanks for the screenshots, and that is weird.  From what I can see here issues OC-3099 and OC-4339 should be listed in the Release report for SD_SDL_R2.0.0.0

I tested this out again on matching versions and was not able to reproduce the behavior so there is something erring, or a data configuration causing the disconnect and we will need to take a closer look at the instance to see what is occuring.

To do this I have created a support request on your behalf viewable at the following link so we can get logging in our secure support portal and figure this one out:

• https://getsupport.atlassian.com/servicedesk/customer/portal/28/JPO-3435

Regards,
Earl