Forge Extension Sprint for small Atlassian gaps

The aim is a small extension that does one thing properly and that someone other than its author can maintain. Neither you nor your customer should end up owning an internal Forge product forever because a gap needed closing once.

This is not broad consulting, and it is not an implementation project without an end. If Jira, Jira Service Management, Confluence or Automation can already close the gap, you are told so during scoping, and nothing gets built.

Four kinds of work fit the format well at the moment.

Private Connect apps that must move to Forge

Atlassian's end of support for private Connect apps begins on 31 January 2027. After that, Atlassian addresses only critical security vulnerabilities in Connect, Connect features can be deprecated at short notice, and apps left on Connect may not keep working as expected. A small private Connect app, such as a panel, a webhook handler or a scheduled job, is often a single sprint on Forge. Where Forge cannot do what the Connect app did, that comes out in scoping, not halfway through the build.

Apps built with Rovo Studio or by AI, before production

Rovo Studio and coding assistants make a working Forge app quick to produce. Whether it is safe to run is a separate question. A review covers the manifest's scopes and egress, permission checks in every resolver, identity and project taken from platform context rather than from what the browser sends, storage and deletion of personal data, and error handling. You get the findings in writing and, if you want them, the fixes.

Jira Service Management portal and request flows

Actions and panels on the customer portal, extra steps around raising a request, and small request-flow changes the portal does not offer natively. Recurring Requests, Eriksen Labs' own JSM app, is built on the same portal extension points.

Builds that must keep data inside Atlassian

When a customer's security review rules out sending data to a vendor's servers, the extension is built on Forge with no external egress and its data in Atlassian-hosted storage, designed to meet the Runs on Atlassian requirements where the feature allows it. Eriksen Labs' own Mermaid Diagrams & Gantt and Recurring Requests carry the Runs on Atlassian badge on the Marketplace.

1. Scoping. A short call, or notes by email if that suits you better. You describe the gap, what the customer has tried natively, and any existing app or prototype.
2. Fixed scope and fixed price. A written scope of about a page: what the extension does, what it does not do, the Forge modules and permission scopes it needs, how it will be tested, and the price. Nothing is built before you agree to it.
3. Build. Built and tested on a development site, with working builds to try along the way rather than status reports.
4. Handover. The source code, a short technical document, and instructions for deploying and upgrading it. The app is deployed under the Atlassian developer account you or your customer choose, so it never depends on Eriksen Labs' account.
5. Maintenance, if you want it. Optional, and agreed separately.

Sprints start at EUR 6,000 (about USD 6,700) for a one-week build, and bigger builds cost about EUR 6,000 per week of work. Each sprint has a fixed price, set in the written scope before work starts. It changes only if the scope does, and only when you agree to the change.

Payment comes in two parts: 50% when you accept the written scope, and 50% when the extension passes the tests written into it. You never pay in full for something that does not work.

• Scoping: EUR 1,000. For work that is not clear yet, including an assessment of an existing Connect app. Credited in full if the build is ordered within 60 days. Clear requests get a fixed quote after a free 30-minute call.
• Moving a private Connect app to Forge: from EUR 9,000, fixed after the assessment.
• Hardening an app built with Rovo Studio or an AI tool: from EUR 3,000.

Atlassian Solution Partners: ask for partner rates. Your customer stays your customer.

If the work does not fit a sprint, you hear that during scoping, with the reason.

Prices are in EUR and exclude any VAT. Invoices can be issued in USD, GBP or NOK on request.

You receive the complete source code. On payment, ownership of the code passes to you or to your customer, whichever the scope names. The extension contains no licence check, remote switch or service hosted by Eriksen Labs, so it keeps working whether or not Eriksen Labs is involved afterwards.

Maintenance is optional: 20% of the build price per year, minimum EUR 1,500, paid yearly. It keeps the extension working as Atlassian changes Forge: platform and API updates, security and dependency fixes, and fixes to what was delivered. New features are quoted as a new sprint. If Atlassian retires something and the extension needs a rebuild, that is quoted separately. Cancel any time before renewal.

Without a maintenance agreement, the handover documentation is written so that you, your customer or another Forge developer can take the extension over.

• Broad Atlassian consulting, estate-wide audits and licence reviews
• Long implementation projects, and Server or Data Center to Cloud migrations
• New Connect apps, and anything that needs a server Eriksen Labs would host and run
• Server and Data Center apps
• Rebuilding what Jira, Jira Service Management, Confluence or Automation already do natively
• First-line support for the customer's users, which stays with you
• Open-ended retainers without a defined scope

Email [email protected] with:

• The product: Jira, Jira Service Management or Confluence Cloud
• What the customer is trying to do, and what they have tried natively
• Any existing Connect app, Rovo Studio app or prototype
• The date that matters, if there is one

Eriksen Labs is a one-person company in Norway, so the reply comes from the person who would do the build. Replies normally come within two business days.

Looking for an existing app instead? The partner page lists the three apps, when each one fits, and when native Jira or Automation is the better answer.