Problem fixed in Jumbo, but not mentioned

[JozkoMrkvicka]

Hello,

Every fix/feature should have some ID, which is mentioned within "List of All Resolved Issues and New Features" for specific GAIA version of Jumbo.

Once there is some ID known (provided by TAC), I often check if it is, or will be, fixed in specific Jumbo Take.

So far it was 100% reliable and the IDs were reported in the list of resolved issues.

During one of recent TAC case where issue ID was provided, it was claimed that issue is already fixed in previous Recommended Take, while the issue itself was not oficially mentioned as fixed. We have proven that the issue is really fixed in Take mentioned by TAC, but I was impressed that it was "hidden" from the list of resolved issues.

Does it mean that Check Point is not mentioning all issues which are fixed in specific Jumbo Take (the real number of issues) ?

[PhoneBoy]

In most cases, yes, the relevant ID should be listed in the fixed issues portion of the JHF notes.
A “fix” usually has a different ID in different releases, so it’s possible it’s listed under a different ID.
If you post the relevant ID (or send in PM) I can have a look.

[JozkoMrkvicka]

PRHF-35676 fixed in R81.10 Take 158 and R81.20 Take 79.

[PhoneBoy]

I've asked Release Management about this PRHF.
I was only able to find one TAC case that mentions this, and it mentioned the lack of documentation about it in the JHF notes.

[the_rock]

That happened to me once when working with a customer back in R77.10 version, where TAC gave us ID number provided by R&D, but was not actually listed in the documentation. I never really inquired about it much, since I logically assumed it was some sort of "custom" thing, but I get the point you are bringing, its totally valid, in my humble opinion 🙂

Andy

[AkosBakos]

Same here. I had such kind of experiences. Last, in R81.10 take 125 had brought some "interesting" issue around SecureXL, which was repaired is take 131.

This was a memorable situation. And there was no mention in resolved issues.

Akos

[Lesley]

Also happens sometimes to me. I think if they add everything they change it will be maybe an unreadable list of information. If a very rare bug is solved and only affects very little customers is it worth to add it and make it more difficult to read. Not sure in this specific case. 
I never believe release notes. ‘We made app more stable’ and then release a 500mb patch 😄

Also maybe worth to send feedback in the relevant jumbo hotfix page. 

 

[JozkoMrkvicka]

If there is very rare issue affecting couple of customers, then there is portfix for such a scenario. Is Check Point more inclined to create portfix each and every time the affected customer(s) asked for ? Or better approach is to integrate it into jumbo and spend the saved time for something else ?

Out of curiosity, I would like to see statistics how many custom portfixes were created in last month for R81.10 and R81.20, which are not planned to be integrated into Jumbo.

[PhoneBoy]

The criteria for including a fix in a Jumbo Hotfix (JHF) typically involves the following considerations:

• Stability and Quality: The fix should enhance the stability and quality of the product. It should resolve known issues that affect the performance or reliability of the software.

• Severity of the Issue: The severity of the issue being addressed is a key factor. Critical vulnerabilities or significant bugs that impact a large number of users are prioritized for inclusion.

• Customer Feedback: Feedback from customers and support cases can influence which fixes are included. If a particular issue is frequently reported, it may be prioritized for a Jumbo Hotfix.

• Testing and Validation: Before a fix is included in a Jumbo Hotfix, it undergoes rigorous testing to ensure that it resolves the issue without introducing new problems.

• Compatibility: The fix must be compatible with the existing software versions and should not conflict with other fixes or features.

Bottom line: it depends on the nature of the problem and the fix itself. 

[JozkoMrkvicka]

Thank you for details.

I expected to see some point related to contract and support level. Having diamond support may be the right trigger to have fixes solved in very short period of time, since customer is paying for such an extended support. The same may apply for paid services, like some blades require additional paid license to function. If there is a bug in that paid service, I can imagine the support has higher focus on it.