Closed releases not visible when using custom section filters

Sunday, October 29, 2023
Avatar

Hi,

We have a suite of custom reports that rely on the Release control in the custom section filter to work which has been working great (once I learnt about the ${ReleaseAndChildIds} token anyway).   However, recently we've started marking releases as Closed to prevent QA from accidentally executing against old releases but this seems to result in the closed releases not being selectable in the reporting filters.

So my questions are:

  1. Are closed releases being deliberately filtered out of report filtering functionality?
  2. If this is a bug what are the chances of a fix?  
  3. Is there a work around? (One that ideally that doesn't involve reopening any release artifacts we want to report on, or even worse, having to hard code requirement ID's to report on historical releases)

Any guidance would be appreciated.

Regards,

Brad.

2 Replies
Monday, October 30, 2023
Avatar
re: bstraka Sunday, October 29, 2023

Thanks for your questions:

  1. Yes that is correct, so they don't clutter up the filters, that is by design
  2. N/A
  3. You could try leaving the Releases as 'Completed' vs. 'Closed'.

I'm afraid I'm not sure of other options. I'd log a support ticket to get additional guidance - https://www.inflectra.com/Support/Ticket/List.aspx

Monday, October 30, 2023
Avatar
re: inflectra.david Sunday, October 29, 2023

Thanks for the quick response David.

I did try using Completed and while that locks down the release form, it won't stop QA assigning new runs against that release which is what we are trying to prevent.

I'll have a chat with the powers that be here in the office and see if we want to go down the ticket route.

Regards,


Brad.

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885

 

Statistics
  • Started: Sunday, October 29, 2023
  • Last Reply: Monday, October 30, 2023
  • Replies: 2
  • Views: 959