Build
Forge apps — Custom UI, resolvers, storage and Rovo modules — built to Atlassian's own platform rules so they keep working after the next platform update.
Independent Atlassian engineering
Nobody wrote it down, the person who set it up has moved on, and every team has since built a workaround. We fix that as engineers — not as a reseller, and not with a slide deck.
The actual problem
A workflow added for one team becomes the default for forty. A field made mandatory during an audit is still mandatory six years later. Automation fires against schemes nobody remembers creating, and permission schemes multiply until no one can say who can see what.
None of this appears as an incident. It appears as delivery getting slower, and nobody able to explain why.
Evidence, not a brochure
GovernScore is ours. It reads a Jira instance and reports what that instance is actually configured to do — measured against 14 control points, checked continuously rather than once during a review.
We built it because we kept doing the same audit by hand. It is exactly the work this practice does, turned into software — which means the review you get here is the one we trusted enough to productise.
See GovernScoreGovernScore
14
control points, checked continuously
GovernScore is a SolutionsCrafters product. It is not an Atlassian product. Jira is a trademark of Atlassian.
What we actually do
Forge apps — Custom UI, resolvers, storage and Rovo modules — built to Atlassian's own platform rules so they keep working after the next platform update.
Integrations over the REST APIs and webhooks, into the systems you already run: finance, CRM, service desks, data warehouses, whatever the process actually touches.
Workflow engineering, automation and ScriptRunner — including removing automation that has outlived its purpose, which is usually the higher-value half.
Governed Cloud migrations and validated bulk operations. Governed means every change is reversible, rehearsed on a copy, and verified against a count you agreed beforehand.
Jira Service Management configuration, platform architecture, and security and health reviews that end in a prioritised list rather than a score.
Documentation, training and a handover written for the person who inherits it. If your team cannot maintain what we built, we have not finished.
How this usually starts
We read the instance and tell you what it is configured to do, what has drifted, and what to fix first. Fixed scope, agreed before we start. Most engagements begin here because most decisions are cheaper after it.
A Forge app or an integration with a defined outcome — the thing your teams keep asking for and the platform does not do out of the box.
Server or Data Center to Cloud, rehearsed on a copy first, with the cutover plan and the rollback written down before the date is booked.
A standing arrangement for teams whose platform is genuinely load-bearing and needs someone who already knows it.
Who does the work
Oday Rafeh has spent 7+ years on enterprise Jira and Confluence — architecture, governance, migration, implementation, documentation and enablement, in environments running several hundred projects at once.
That experience is his, personally. SolutionsCrafters is a young studio, and we keep those two facts separate on purpose — a company that borrows its founder's CV for its own age is telling you something before you have even started.
Founder on LinkedInNext step
The instance everyone complains about is the one worth looking at first. Tell us what it does and what it should do, and we will tell you honestly whether we are the right people for it.
SolutionsCrafters is an independent consultancy. It is not affiliated with or endorsed by Atlassian, and it is not an Atlassian Solution Partner. Atlassian, Jira, Confluence and Forge are trademarks of Atlassian Pty Ltd, used here only to describe the platforms we work on.