Atlassian Cloud apps from trusted architects

We work with banks, ministries and enterprises. Every app began as a gap we found while running a client’s Atlassian ecosystem.

See our applications How we handle data

assessed hundreds of applications for clients before we built our own: Solution architects
the applications run inside your own Atlassian site, on Atlassian’s infrastructure, never on ours: Atlassian Forge
Monday to Friday, from the person who wrote the code: Reply within 24 hours

What hundreds of evaluations taught us

Four problems we kept finding in the apps we assessed

01 · Fragmentation

The capability is split across several vendors

One application solves part of the problem and another solves the rest. We have sat in the meeting where we set out those shortcomings and the customer has to choose which one to live with.

We build the whole capability into one application, so that choice does not have to be made.

02 · The wrong assumption

It assumes a process nobody actually runs

One project, one workflow, one team, one approval step. Real instances are made of exceptions, and a feature built without them makes you change how you work to suit the application rather than the other way round.

Ours are specified from processes we ran, exceptions included.

03 · The missing detail

One small thing is missing, and it is the one you need daily

Not the headline feature. The field that cannot be cleared, the value that does not survive a save, the bulk action that handles nine rows and stops. Small enough to miss in an evaluation and large enough to matter every day.

Those are the first things we specify, because they are the ones we hit.

04 · Out of place

You can see where native Jira ends and a third-party app begins

Different buttons, different spacing, its own words for things Jira already has a word for. It works, but it never looks like part of your site.

Ours use Atlassian’s own components, so the app will feel familiar.

The applications

What you can install today

Oktul Work Item Selector for Jira

A single- or multi-select Jira custom field that offers only the work items a JQL query returns, with dynamic values for the current user and work item.

What it does Marketplace Documentation

A work item whose Related Work Items field shows two selected work items as rows, each with its key, summary, priority, status and assignee. — Oktul Work Item Selector for Jira, captured in Jira Cloud

The roadmap comes out of consulting work, so a gap you describe can end up on it. Tell us what yours is

Experience

Our roadmap comes from our clients' Atlassian ecosystems

Our applications come out of implementation and administration work, not a product team, so we build applications that solve the problems we keep running into ourselves.

Hours implementing the Atlassian platform: 14,000+; Combined across the team, in the public and private sector.
Years of experience as architects: 7+; Jira and Jira Service Management administration, migrations, integrations and custom solutions.
Atlassian certifications and accreditations: 23; Designations, certifications, accreditations and credentials. The company page lists the designations and certifications, each with the month it was awarded.

Our apps are made by admins, for admins

Setting up our applications follows the same logical path as Atlassian's own. The documentation is part of the application and we keep it current, so common questions are answered quickly. If you have questions, we are always ready to help.

See our applications Contact us