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
Your Jira does what someone configured it to do years ago
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.
- 7+ years founder experience
- Environments with several hundred projects
- English · Nederlands · العربية
The actual problem
Jira rarely breaks. It accumulates.
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.
- Workflows nobody can justify, kept because changing them feels risky
- Required fields that exist to satisfy an audit that finished years ago
- Permission and notification schemes that have quietly diverged
- Automation running against configuration it was never designed for
None of this appears as an incident. It appears as delivery getting slower, and nobody able to explain why.
Evidence, not a brochure
We turned our own audit into software
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
Six kinds of work, from a Forge app to the handover
Connect
Integrations over the REST APIs and webhooks, into the systems you already run: finance, CRM, service desks, data warehouses, whatever the process actually touches.
Operate
Workflow engineering, automation and ScriptRunner, including removing automation that has outlived its purpose, which is usually the higher-value half.
Move
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.
Govern
Jira Service Management configuration, platform architecture, and security and health reviews that end in a prioritised list rather than a score.
Enable
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
Four shapes, scoped before anyone commits
- 01
A health review
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.
- 02
A build
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.
- 03
A migration
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.
- 04
Ongoing engineering
A standing arrangement for when the platform is load-bearing and the next change should not begin with someone learning the instance from scratch.
Who does the work
Seven years inside other people's Jira
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 LinkedInPackages
What it costs
A fixed-price diagnostic that ends in a written, ranked list. The work it finds is billed by the hour, scoped from what the diagnostic actually found.
Jira Health Scan
Somebody asked whether your Jira is in good order and you have no defensible way to answer.
€950fixed
Excluding BTW · 5 working days
You receive
A 0–100 score with an A–F grade, the evidence behind every finding, and a ranked list of what to fix first.
- 46 deterministic rules across Configuration, Security and Usage
- Read-only. Nothing changes, so there is no change window to book.
- One row per Jira object listing every rule it trips
- A coverage report naming every check we could not run. Those are left out of the grade, not marked as passed.
- A 90-minute read-out with your team
Then€125per hour· typically 40–80 hours
Working the remediation list: schemes consolidated, permissions narrowed, custom fields retired, filters and dashboards cleaned, licences recovered.
Who it is for: Jira administrator, platform owner, IT governance lead
Atlassian Integration
Jira does not talk to the system where the work actually gets paid for, so somebody retypes it.
€1.200fixed
Excluding BTW · 1 week
You receive
An integration design: the data that moves, in which direction, what happens when either side is down, and a fixed estimate for the build.
- Both systems mapped, field by field
- Failure and retry behaviour decided before anything is built
- Build target chosen and justified: Forge app, Connect, or middleware
- A written estimate you can approve or walk away from
Then€125per hour· typically 60–120 hours
Building, testing and handing over the integration, with the failure paths exercised rather than assumed.
Who it is for: Operations or finance lead who is tired of double entry
Next step
Send us the messy one
The instance everyone complains about is the one worth reading first. Tell us what it does now and what it should do, and we will say plainly whether this is work we should take.
Independence
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.