Where to report bugs outside of the case portal

[jtompkins]

Hi,

Was wondering what the best forum is for reporting bugs that is NOT the case portal? There should be a way to do this without having to create individual support cases, which just creates an additional burden for the users. For example if I created a support case for every bug I found, I would have dozens in my queue at any given time, which I would like to avoid.

To provide an example of a general-enough bug in Compose: 

When using a view as a lookup table in a map, if you go back into that lookup editor and are brought to the "Select Lookup Table" screen, the view that was initially selected doe not "stick", and the display defaults to the table list where the first table alphabetically appears in the dropdown. This is an obvious source of confusion because it is no longer clear what is being used as the lookup table.

[Nanda_Ravindra]

@jtompkins I understand your point regarding the additional burden for the users to open a case. But the only way to keep track of the bug is by getting the case in the support portal.

What version of Compose are you running? We have several UI bug fixes in the newer version

Thanks,

Nanda

[jtompkins]

I kind of knew that would be the response but was hoping not. I am on 2021.8.0.372. For every bug a new version fixes, a dozen more are introduced, which is why we are reluctant to upgrade.

[Nanda_Ravindra]

@jtompkins I understand your concern, I checked the latest release notes and accumulated release notes for both 2021.8 and 2022.5 and I am not seeing any reference to the issue you are reporting. So, it looks like you found a new issue that no one has reported.  Please open a case with support so we can account for this issue and have  R&D take a look into this new issue you are reporting.

Thanks,

Nanda

[jtompkins]

There is another issue with maps where when you change the source schema of the table/view/query and then go to migrate the change to a different environment, the target environment will "not find" the new target table/view/query because the source schema will still be set to what it was originally. If you try changing it manually, the map gets wiped.

Should this be a different case or lumped with the other?

Opening cases for bugs like these and all the follow-up that entails would constitute a full-time job.

[Nanda_Ravindra]

@jtompkins I totally get what you are saying. Most of what you are seeing seems to be a UI-related issue. I would suggest opening separate cases so we don't lose track of the issues.

Thanks,

Nanda