Skip to content
Exobean

SLACredit administration and user guide

Complete guide to installing, configuring and operating SLACredit for Jira Service Management, covering contracts, credit rules, the breach ledger, waiver approvals, backtesting, SHA-256 period locking, data residency, billing and troubleshooting.

SLACredit v1.0 Atlassian Marketplace Updated 2026-11-16 Product overview

Overview

SLACredit is a commercial software application for Jira Service Management (Cloud) that converts SLA breaches into governed financial outcomes. It is built on Atlassian Forge and runs entirely inside Atlassian Cloud. This guide is written for Jira administrators, service delivery managers, finance reviewers and approvers.

Roles referenced in this guide:

Role Where it is defined What it can do in SLACredit
Jira site administrator Atlassian administration Install, configure global settings, lock periods
Project administrator Jira project roles Link a JSM project, manage its contracts and rules
Approver SLACredit waiver settings Approve or reject breach exemptions at an assigned step
Agent JSM agent licence View the ledger for projects they can access
Finance reviewer SLACredit ledger settings Export ledgers and verify period locks

Installation from the Atlassian Marketplace

  1. Sign in to your Atlassian site as a site administrator.
  2. Open Apps → Find new apps and search for SLACredit, or open the Marketplace listing linked from the product page.
  3. Choose Try it free to start the Marketplace-managed evaluation, or Buy it now to begin a subscription.
  4. Review the Forge permission summary. SLACredit requests read access to Jira issues and SLA data and write access to its own Forge storage. It declares no external egress permissions.
  5. Confirm installation. The app appears under Apps → SLACredit in the top navigation and as a project page in each linked JSM project.

Installation typically completes within a minute. If the app does not appear, refresh the page and confirm that the installing account holds site administrator rights.

Linking Jira Service Management projects

SLACredit only governs projects you explicitly link.

  1. Open Apps → SLACredit → Projects.
  2. Choose Link project and select a Jira Service Management project.
  3. Select the SLA definitions in that project that should be eligible for credits (for example Time to first response and Time to resolution).
  4. Save. SLACredit begins reading SLA cycle data for the project from the moment it is linked. Historical issues are indexed on first link and available for backtesting.

A project can be unlinked at any time. Unlinking stops breach detection but retains the ledger for locked periods.

Contracts and credit rules

A contract represents the commercial agreement with one client (for MSPs) or one business unit (for internal IT).

Creating a contract

  1. Open SLACredit → Contracts → New contract.
  2. Enter the contract name, the client identifier used on invoices, the currency and the billing period (monthly or quarterly).
  3. Map the contract to one or more JSM projects, organisations or request types so SLACredit can attribute each issue to the right contract.
  4. Set the contract effective dates. Only breaches inside the effective window are attributed.

Credit rules

Each contract holds an ordered list of credit rules. A rule defines:

  • Trigger: the SLA definition and priority that must breach.
  • Calculation: fixed amount per breach, percentage of the period fee, or a tiered schedule by breach duration.
  • Cap: a maximum credit per breach, per period, or both.
  • Grace: an optional tolerance in minutes before a breach counts.

Rules are evaluated top to bottom; the first matching rule applies. Use the Preview action on any rule to see how it would score the last 50 breaches before saving.

Operating the breach ledger

The Breach ledger tab lists every breach attributed to a contract in the current open period.

Each row shows the issue key, client, SLA, breach duration, calculated credit and status. Statuses are:

Status Meaning
Detected Breach detected and scored; no action yet
Credited Credit confirmed and included in the period total
Waiver pending An exemption request is in an approval step
Exempted Exemption approved; credit excluded from the total
Rejected Exemption rejected; credit stands

Filter by contract, SLA or status, and open any row to see the full SLA cycle timeline from Jira alongside the rule that produced the credit.

Waiver and exemption approvals

A waiver removes a breach from the credit total with a recorded justification.

  1. From a ledger row choose Request waiver, select a reason category and write a justification.
  2. The request enters the approval chain configured under Settings → Waiver workflow. A chain has one to five steps, each assigned to a Jira group or named approvers.
  3. Approvers receive a Jira notification and act from the Waivers tab. Each decision records the approver account, timestamp and comment.
  4. When the final step approves, the breach moves to Exempted. A rejection at any step returns it to Credited.

All waiver history is retained and exported with the ledger.

Contract backtesting

Backtesting applies a proposed rule set to historical data so you can see the financial effect before committing to it.

  1. Open Contracts → (contract) → Backtest.
  2. Choose a historical window (up to 24 months of linked project history).
  3. Edit the rule set in the backtest editor. The live contract is not changed.
  4. Run the backtest. SLACredit scores every historical breach and reports total credits, credits by SLA and the top contributing issues.
  5. Choose Apply to contract to replace the live rules, or discard.

Period locking with SHA-256 verification

Locking a period freezes the ledger for invoicing.

  1. Open Period locks and select the period to close. All waivers must be resolved first; the lock action lists any that are still pending.
  2. Choose Lock period. SLACredit writes an immutable snapshot of every ledger row and computes a SHA-256 digest over the canonical snapshot.
  3. The digest is displayed on the period and included in every export.
  4. Every time a locked period is read, SLACredit recomputes the digest from stored rows and compares it. A mismatch is shown as Verification failed and should be reported to support.

Unlocking requires a site administrator and is recorded with a reason. The original digest remains in the audit history.

Exports

From Breach ledger or Period locks choose Export. Exports are available as CSV and as a structured JSON document. Each export includes the contract, period, rule version, every ledger row, waiver history and the period digest where locked. Exports are generated inside Forge and downloaded directly by your browser; nothing is sent to Exobean LLP.

Data residency and zero-egress FAQ

Where does SLACredit store data? In Forge SQL and Forge Key-Value Storage provisioned for your Atlassian site, in your site’s Atlassian Cloud region.

Does any data leave Atlassian? No. The app declares no external fetch permissions and cannot call external services.

Does Exobean LLP have access to our data? No. Exobean LLP has no operational access to Forge storage for your site.

What personal data is processed? Atlassian account identifiers of agents, approvers and requesters, and the comments written in waiver requests. Profile details are resolved by Jira at display time and are not stored by the app.

Is the app covered by Atlassian’s Runs on Atlassian program? SLACredit is designed to the program’s requirements. The current program status is displayed on the Marketplace listing.

Billing, trial and uninstallation

  • Licensing is a per-agent monthly subscription billed by Atlassian through the Marketplace. Agent count follows your Jira Service Management licence.
  • The evaluation trial is managed by Atlassian; no card is required to start it.
  • Invoices, tax and payment questions are handled by Atlassian. Commercial questions about the licence itself may be sent to billing@exobean.com.
  • To uninstall, open Apps → Manage apps, find SLACredit and choose Uninstall. Atlassian removes Forge storage according to its storage lifecycle. Export any locked periods you need before uninstalling.

Troubleshooting

Symptom Likely cause Resolution
Project not listed when linking Project is not a JSM project or you lack project admin rights Confirm the project type and your role
Breaches not appearing No SLA definitions selected, or issue outside contract effective dates Review the project link and contract dates
Credit is zero Rule grace exceeds the breach duration or no rule matched Use rule Preview to confirm matching
Cannot lock period Pending waivers Resolve all waivers listed on the lock dialog
Verification failed on a locked period Stored rows differ from the snapshot Do not unlock; contact support with the period identifier
Approver did not receive notification Jira notification scheme filters app notifications Check the user’s notification settings in Jira

For anything not covered here, open a request at the Exobean service desk or write to support@exobean.com with your site URL, the app version shown in Settings → About and the steps you followed.