Public bug / problem tracker
95
Views
6
Comments
New
Community

A propose a public bug tracker for issues in the OutSystems platform.

I understand why OutSystems would be reluctant to do this but here's some advantages:

  • Transparency: a public bug tracker shows commitment to transparency and accountability, building trust with the community and customers.

  • Community Collaboration: it allows users to report bugs, suggest fixes, and contribute to the platform's development.

  • Improved Communication: users get visibility into the status of reported bugs, avoiding redundant reports.

  • Prioritization by Demand: users can vote on issues they care about most, helping OutSystems prioritize fixes based on real-world demand.

  • Knowledge Sharing: a public bug tracker serves as a centralized knowledge base where users can search for known issues and workarounds.

(Disclaimer: an LLM did help me write some of this)

The motivation of this idea comes from the time wasted recently creating support cases for problems that were already identified by the OutSystems team. Many of these problems have forum posts with dead ends, where people were left without an answer.

I would imagine this would also free up time from the support team.

Cheers,

Tiago

The Problem List is already available, not publicly, but once you have logged in with your community action, on the Problems List tab.

@Daniël Kuhlmann I'm aware of that. My idea is to have a public version.

The current version has none of the benefits I mentioned: transparency, community collaboration, improved communication, prioritization by demand and knowledge sharing.

Why does it need to be public? I am pretty sure the information is only relevant for someone using OutSystems not just everybody on the planet.

Public in the sense that I (as a community member) could see problems associated with cases you created, and the other way around.

For example, I recently found a bug related with scroll in mobile screens that use tabs. I looked in the forums for answers and found the exact bug reported back in 2020.

It was my decision to go back to that post and inform the community that it is being worked on and the problem associated with it so I can help people that stumble upon the same problem. Don't you think that if the problem tracker was shared between community members all this back and forth would be greatly simplified, saving everyone's time?

Hope it makes sense

Cheers

The link you shared is from the time the Problem list was not yet possible.

The Problem list is available for people working on a paid OutSystems license.

Sorry @Daniël Kuhlmann, I'm not sure I follow what you mean and how it relates to the viability of my idea.

The problem list exists. The problem list is not shared between community members (with paid license).

My idea is to share that problem list between every OutSystems customer, so everyone can benefit from reported bugs, suggested workarounds, etc., as mentioned in my original post.