Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello all,
I have a quick question about appropriate interpretation of release notes. If you pull up latest release notes for Qlik Sense April 2020 (Patch 5), it mentions "Fixed dimension label visibility, Jira issue ID: QB-1059" twice - once in initial release and once in Patch 4.
This "Resolved Issue" was also mentioned:
and potentially in release notes from older versions (I only went back to November 2019). QB-1059 is not the only resolved issue that is repeated across different versions and patches of Qlik Sense.
Does anyone know what's the meaning of repeating "Resolved Issues" in release notes?
Continuing on with April 2020 Qlik Sense as an example, if I installed the initial release which had the QB-1059 fixed and then two or three months later I installed Patch 3 of April 2020, does that mean that this issue was brought back? Does that mean that if I want this issue fixed, I'll have to either roll back to initial release of April 2020 or upgrade to Patch 4 of April 2020 release?
Thanks,
Mikhail B.
Hi @mgranillo,
I spent a bit over two months with Qlik support trying to figure out what was happening there. The answer is that they release the same fix for several different versions of their software. They do that because they know that their clients may not necessarily be running the latest and greatest version of Qlik Sense. Some may have February 2021 version and others may still have November 2019 installed. A bug, however, may exist in both February 2021 and November 2019 and several other versions of their software. So what they do is fix the bug in November 2019 and February 2021 and in whatever other versions the bug exists and publish release notes for different versions of their software wherever that bug was fixed.
If a fix shows up on release notes for prior versions of Qlik Sense it doesn't mean that the issue was brought back later, it means they didn't want to leave their clients running older versions of Qlik Sense without a fix so they fixed the issue not only in the newest version but also in several older versions.
As for Jira issue ID: QB-1059 showing up in both initial release of April 2020 and April 2020 Patch 4, apparently the fix released in initial release didn't fully fixed the problem so they for real, for real fixed it in April 2020 Patch 4. That's the story there. I hope this helps!
Mikhail B.
I noticed this as well and have the same questions. Unfortunately, looks like no one has an answer
Hi @mgranillo,
I spent a bit over two months with Qlik support trying to figure out what was happening there. The answer is that they release the same fix for several different versions of their software. They do that because they know that their clients may not necessarily be running the latest and greatest version of Qlik Sense. Some may have February 2021 version and others may still have November 2019 installed. A bug, however, may exist in both February 2021 and November 2019 and several other versions of their software. So what they do is fix the bug in November 2019 and February 2021 and in whatever other versions the bug exists and publish release notes for different versions of their software wherever that bug was fixed.
If a fix shows up on release notes for prior versions of Qlik Sense it doesn't mean that the issue was brought back later, it means they didn't want to leave their clients running older versions of Qlik Sense without a fix so they fixed the issue not only in the newest version but also in several older versions.
As for Jira issue ID: QB-1059 showing up in both initial release of April 2020 and April 2020 Patch 4, apparently the fix released in initial release didn't fully fixed the problem so they for real, for real fixed it in April 2020 Patch 4. That's the story there. I hope this helps!
Mikhail B.