We sometimes find minor bugs when using Matillion. For example we just recognized that the version number of a shared job component is not shown in the UI for longer job names. This is not critical but could improve consistency and usability if it is fixed.
Of course, we open a support ticket if we have business critical bugs with higher priorities. But what do we do with these minor issues?
Do you think it is a good idea to have a public bug tracker (like we now have for feature requests on the ideas portal)? I think this could also help to maintain a list of "known issues" for the releases. Also, the community could help to confirm and reproduce bugs and also set priorities.
@all (Matillion and customers), what's your opinion?
This is a brilliant question, how we do this has been the subject of some internal discussions and something we are considering! It would be amazing to hear what other users think and please fire over any ideas and suggestions you have for this. I know I mention it a lot but your feedback on these kinds of changes are priceless to us and help us ensure our users have the best experience.
@Michael and @JoeCommunityManager, I like the idea of a bug tracker. We have also wondered what the appropriate method of reporting bugs would be. If it's not a bug tracker, just knowing what the appropriate method of reporting bugs is, would be beneficial.