ENET
Marketplace (opens in a new tab)

We ran Atlassian Cloud before we built apps for it.

We build Atlassian Cloud applications for banks, ministries and enterprises. Each began as a gap we hit running somebody else’s Jira.

assessed hundreds of applications for clients before we built our own
Senior consultants
the applications run inside your own Atlassian instance, on Atlassian’s infrastructure, never on ours
Not our servers
the person who answers your ticket is the one who wrote the code
Ready to support
What hundreds of evaluations taught us

Four ways an application fails in production, and what we do instead.

01 · Fragmentation

The capability is split across two vendors

One application does half of it well and another does the other half. We have sat in the meeting where we set out the shortcomings of each 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 tell which screens are not Jira

Different buttons, different spacing, its own words for things Jira already has a word for. It works, but every person using it can see exactly where your instance ends and the app begins.

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

The applications

Named here once there is a listing.

An application appears here once it has an Atlassian Marketplace listing, and not before: a disclosed roadmap is worth more to a competitor than the marketing is worth to us.

Work Item Selector for Jira Cloud

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.

Editing the field
PLAT-204OKT-14Search work items…
On the work item
  • PLAT-204In ProgressKK
  • OKT-14DoneJT
Drawn from the application's own components, not captured

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

Experience

We ran other people's Atlassian platforms first.

We came out of implementation and administration work rather than a product team, which is why the roadmap is a list of gaps we hit rather than features we thought would sell.

Hours implementing the Atlassian platform
14,000+
Combined across the team, on public and private sector programmes before the first product shipped.
Years each, in Atlassian delivery
7+
Jira and Jira Service Management administration, migrations and platform integration.
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.

We put as much work into the documentation as into the applications. Both are public, so you can read them before you install anything. Or ask us first.

See our applicationsAsk a question first