Skip to main content
Version: Next

Installation Guide

Installing Admin Essentials for Jira on your Jira Cloud instance is done directly from the Atlassian Marketplace. Follow this guide for a correct setup and to activate your license or free trial.

Prerequisites​

  • You must have Jira Administrator or Site Administrator permissions to install apps on your tenant.
  • An active internet connection and access to your Jira Cloud instance (your-domain.atlassian.net).
  • Jira Service Management (JSM) compatibility: The add-on's custom fields work in JSM spaces, including the agent view and the customer portal.

Admin Essentials for Jira on Atlassian Marketplace

Installation steps (Administrators)​

Follow these instructions to enable the add-on across your organization:

  1. Sign in: Access your Jira Cloud instance (e.g. your-domain.atlassian.net) with administrator credentials.
  2. Explore apps: In the left navigation, open the Apps menu and select Explore more apps or Find new apps.
  3. Search: In the Marketplace search bar, type Admin Essentials for Jira and press Enter, or open the Marketplace listing directly.
  4. Select the app: Open the Admin Essentials for Jira listing published by MB Group.
  5. Start trial or purchase: Click Try it free or Buy now as appropriate.
  6. Confirm permissions: Review the requested scopes and confirm with Start free trial, Accept & install, or the equivalent button.
  7. Verify: In Jira, go to Apps → Manage apps and confirm Admin Essentials for Jira is installed.
Required scopes

The app requests read permissions on fields, contexts, spaces, work types, and priorities, plus read/write permissions on contextual configuration of custom fields (to persist Traffic Light KPI thresholds per context). All scopes follow Forge's least-privilege principle.

Not an administrator?​

If you don't have admin privileges, Atlassian lets you suggest useful tools:

  1. Complete steps 2–4 above.
  2. Select Try it free, then click Submit request.
  3. Optionally add a message explaining why the add-on will benefit your team.
  4. Your administrator will receive a notification to review and approve installation.

Atlassian Marketplace and billing​

1. Free trial​

Paid Marketplace apps typically offer a 30-day free trial with full functionality, equivalent to an active license.

2. Pricing tiers​

  • User-based: Cost is calculated from your Jira site's total user count (user tier), not per individual use of the add-on.
  • Cloud Free plan: On sites with up to 10 users, many apps are free or low-cost depending on tier.

3. Centralised billing​

Atlassian consolidates app charges on the same invoice as your Jira subscription. You don't need separate payments to MB Group.

Official resources

Licensing and support​

From version 4.0.0, the app requires an active Marketplace license to edit fields, configure contexts, and create or modify validators. Data already stored remains visible without a license.

Automatic updates (Forge)​

Unlike Data Center plugins, Forge apps are updated automatically from Atlassian's infrastructure with no manual administrator intervention.

Permission changes

If a version introduces new scopes, Atlassian will notify you and request explicit approval before applying the update. Versions that don't change permissions are applied transparently.

Upgrading to version 1.9.0 / Forge 7.0.0​

Version 1.9.0 (Forge 7.0.0) is a product minor release on top of 1.8.0 (Forge 6.1.0). It adds the colour search JQL functions, the attachment count validator, and two Attachment Field fixes.

The move to Forge 7.0.0 is because the app requests new permissions:

PermissionWhat it is used for
read:app-data:jira / write:app-data:jiraKeeping the trafficLightBand and percentageBand JQL functions up to date when a context's thresholds change
storage:appTemporarily storing the name, size, and type of files uploaded to the Attachment Field from the create screen or the JSM portal, until Jira creates the work item

When the update is published, Atlassian notifies the site administrator and asks them to approve the new permissions. Review and confirm them from Apps → Manage apps → Admin Essentials for Jira. Until they are approved, the site stays on 1.8.0.

The update is compatible with all field and validator configurations from 1.8.0. There is no data migration: context restrictions, native attachments, and the card view are kept. If an Attachment Field context had a Maximum files value greater than 7, 7 applies from this version on (see the Attachment Field guide).

Previous version: 1.8.0 / Forge 6.1.0​

Version 1.8.0 (Forge 6.1.0) was a minor release on top of 1.7.0 (Forge 6.0.0): the Attachment Field started storing new files as native Jira attachments and displaying them as cards. Files uploaded before that version were not migrated: they remain available from the field, but stay in the storage used by version 1.7.0.

Historical note: upgrading 1.6.0 → 1.7.0​

Re-consent for version 1.7.0

Version 1.7.0 (Forge 6.0.0) previously introduced a major Forge version change that added storage of the app's own (Forge Object Store) for the Attachment Field, and required an Update and permission re-consent from Apps → Manage apps. This requirement no longer applies as of 1.7.0 onward: it is documented here only as historical reference for sites that have not yet completed that update.

Next steps

Once installed, visit the Administrator Guide to configure your first custom fields and validators.

Last updated on