Running into problems in Opcenter and wondering if it’s just you? Chances are — it’s not. But without a shared knowledge base, everyone wastes hours re-solving the same issues. That’s why I started the ResolutionTracker GitHub repo: a centralized place for known issues and their resolutions, organized by version and suite.
The Problem We All Face
If you’re not on the latest version of Opcenter, you’ve probably hit bugs or issues that others have already seen. But how would you know?
I kept hearing the same questions from colleagues and clients:
🗨️ “Hey Jan, have you seen this issue before?”
🗨️ “Is this a known bug?”
Most of the time, yes — either I’d seen it, or someone else had. But without a shared reference, we wasted valuable time and eroded client trust.
Why It Matters
Let’s be real: some consultants even treat this as a business model.
❌ Don’t share known issues.
❌ Let the billable hours pile up.
But where’s the challenge in that?
Since there’s no official, comprehensive list of known issues with solutions, we all end up duplicating effort.
The Solution: ResolutionTracker
So I built it.
👉 GitHub Repo – ResolutionTracker
A list of known issues and their resolutions, organized by version and suite.
How You Can Help
💬 Found a bug? Add it.
💬 Solved a pain point? Contribute.
💬 Want to stay up-to-date? Star the repo.
Together, we can stop duplicating work and raise the bar for everyone working with Opcenter.
