Eriksen Labs Support

For Atlassian Solution Partners

We build the apps. You deliver the project.

Three focused apps for Jira, Jira Service Management and Confluence. When a regulated cloud, a security review or an in-house Data Center add-on stands between your customer and the move, we take it off your plate. The customer stays yours.

  • Built on ForgeAll three carry the Runs on Atlassian badge
  • Bought through AtlassianQuoted and ordered like any Marketplace app
  • Free up to 10 usersOn every app, with nothing to ask for
  • No paperworkNo agreement, tier or application

Where we help

Three things that stall a project, and what we do about them.

A regulated cloud

All three apps are listed for Atlassian Isolated Cloud, with the same features as in the normal cloud. In Atlassian Government Cloud, since 20 November 2026: the diagrams app, with Mermaid, PlantUML and OpenAPI, and Issue Templates.

Regulated clouds

A security review

There are no servers of ours to assess, and nothing leaves Atlassian. We answer your customer’s questionnaire in 1–3 business days.

Trust center

Leaving Data Center

Diagrams come across by copy and paste, templates and schedules are set up again, and an in-house add-on can be rebuilt on Forge.

Moving from Data Center

How it works with us

Six promises, kept by the person who makes them.

  1. Buy through Atlassian, with your partner discount

    In Atlassian Cloud, all three apps are in Atlassian’s partner discount program. Quote and order through Atlassian, as you do for any Marketplace app.

  2. Free on your own sites

    Every app is free up to 10 users. For a larger demo or internal site in Atlassian Cloud, up to 100 users, write to us and we send a code.

  3. Security questionnaires, answered

    Start at the trust center. Send your customer’s questionnaire and we return it in 1–3 business days.

  4. A direct line to the developer

    Partner questions get an answer within two business days, in Norwegian business hours, from the developer who builds the apps.

  5. A call with your customer when it helps

    A video call for a demo, or for the questions a customer’s security team wants to ask in person.

  6. In-house Data Center add-ons, rebuilt on Forge

    If a customer’s own add-on is holding up the move, we rebuild it: the first hour free, then from EUR 6,000 per add-on. You keep the customer. We quote your customer directly or work as your subcontractor, your choice.

    Your own add-onsHow the free hour works

What we don’t have

No partner tiers, portal or paperwork. No deal registration, referral fees or certification. If that changes, it will be because partners asked for it.

Field guide

Which app fits?

Start from what the customer describes. Where native Jira, Automation or another kind of tool is the better answer, this guide says so.

The customer describesThe better answer
Engineers already write Mermaid, and the diagrams in Confluence are screenshots nobody can edit.Mermaid & PlantUML Diagrams
OpenAPI or Swagger and other formats, across many teams, in one app.Another kind of tool: a broad technical-content suite
Portal customers want to set up, pause and cancel their own recurring requests.Recurring Requests & Templates
An admin wants the same ticket created on a schedule, for the same team with the same fields.Native: Jira Automation’s scheduled trigger
Issues arrive without what the team needs, and each issue type should start from its own description, without another custom field.Issue Templates & Create Defaults
Filling a field after the issue has been created is good enough.Native: an Automation rule on Issue created
The gap needs a small extension of its own, or a private Connect app has to move to Forge.A fixed-scope build: Forge Extension Sprint

Mermaid & PlantUML Diagrams

Confluence Cloud · Product page · Documentation

When a customer says…

  • “Our engineers write Mermaid in GitHub already. Confluence should render it too.”
  • “The architecture diagrams in Confluence are screenshots nobody can edit any more.”
  • “Security will not approve a diagram app that can read our pages.”
  • “We want the project’s Gantt chart on the project page, kept as text next to the plan.”

What it replaces

  • Diagram screenshots pasted into pages and left to go stale
  • Mermaid kept in code blocks that never render
  • A general-purpose diagram app installed for a team that only ever writes Mermaid

Where it stops

Mermaid, PlantUML and OpenAPI, nothing else. The OpenAPI macro is a read-only map with no Try it out: if the customer wants interactive API documentation, or other formats across many teams in one app, a suite or a dedicated API documentation tool is the better fit. Not a drag-and-drop whiteboard: teams who would rather draw than write text are better served by a drawing tool.

Recurring Requests & Templates

Jira Service Management Cloud · Product page · Documentation

When a customer says…

  • “Our customers email us every month asking us to raise the same request.”
  • “Customers want to schedule their own quarterly access reviews, and stop them when they no longer need them.”
  • “We keep one Automation rule per customer for their recurring requests, and nobody wants to own them.”
  • “A customer should be able to pause it over the holidays without raising a ticket about it.”

What it replaces

  • Customers emailing an agent to raise the same request again
  • Reminders in the customer’s own calendar
  • Per-customer scheduled Automation rules that an admin has to create, change and retire on the customer’s behalf

When Automation is the better answer

An admin owns a simple recurring job, such as the same ticket created every Monday for the same team with the same fields. Jira Automation’s scheduled trigger does that natively. This app earns its place only when the portal customer has to own the recurrence, within limits the admin sets. Attachments are not copied to a repeat.

Issue Templates & Create Defaults

Jira Cloud · Product page · Documentation

When a customer says…

  • “Half our bug reports arrive without steps to reproduce.”
  • “Each issue type should start with its own description, and we do not want another custom field.”
  • “Project admins should look after their own templates without raising a ticket with the Jira admin.”
  • “Every release epic needs the same stories and sub-tasks, and someone always forgets one.”

What it replaces

  • A “how to write a good bug report” page nobody opens
  • Descriptions pasted by hand from a wiki page
  • Scripts or Automation rules kept only to create the same sub-tasks or stories every time
  • A “template” work item that people clone and then forget to clean up

Where it stops

A template is applied when someone picks it on the Templates page, or from a Jira Automation rule with the app’s own actions. Pressing Create opens Jira’s usual form, with a line naming the issue type’s default template. Quick create, email and the REST API never apply one. A named assignee, user-picker fields and versions are left to the person.

Questions partners ask

Is there a partner agreement?

No. Atlassian’s terms cover the purchase, as for any Marketplace app.

What discount do we get?

In Atlassian Cloud, the one Atlassian gives your partner level. We don’t set it.

Do you offer implementation services?

No. We build apps and rebuild in-house add-ons. Configuration and rollout are yours.

Who supports the customer?

We support the app directly. You keep the relationship.

Bring us into your next project.

Write to [email protected] with the customer’s cloud, the app and what is in the way. You get an answer within two business days.

Looking for a partner?

Any Atlassian Solution Partner can set up our apps. Find one in Atlassian’s partner directory.