Skip to main content
addly

Vocabulary should never be a hidden obstacle to purchasing.

This glossary defines the terms needed to examine an Atlassian app. Each group connects product, trust, and operations instead of accumulating definitions for search rankings.

26 essential terms

Marketplace, Jira and Confluence surfaces, security, data, contracts, and operations.

26 definitions across 4 categories.

GROUP 01

Atlassian and Marketplace

6 definitions

Atlassian Marketplace
The official catalog where customers discover, evaluate, and acquire Atlassian apps.
Marketplace listing
An app’s official page: vendor, hosting, versions, prices, reviews, security, and support.
Cloud hosting
Hosting operated as a service; the architecture and processing may differ from a Data Center app.
Data Center deployment
A deployment self-managed by the customer in its own infrastructure, with specific versions and compatibility.
User tier
The license bracket used by Marketplace to determine price according to site size.
Forge platform
Atlassian’s platform for developing and running apps with documented modules, scopes, and constraints.
GROUP 02

Product surfaces

6 definitions

Issue panel
An area in a Jira issue where an app can display contextual information or an action.
Project page
A page added to a Jira project for a project-level view or workflow.
Content macro
A component inserted into a Confluence page and configured with that page.
Context panel
A Confluence side panel that complements the page without replacing its primary content.
Degraded mode
The planned behavior when required data, permission, or a service is missing.
Empty state
The first useful state of a surface before any configuration or usable data exists.
GROUP 03

Security and data

8 definitions

Permission scope
A declared permission allowing an app to read or modify a category of Atlassian resource.
Least privilege
The principle of requesting only the access required for the observed function.
Data residency
Control or information about the region where certain covered data is hosted.
Retention
How long data remains stored before deletion or anonymization.
Subprocessor
An organization that processes data for a controller or another processor.
Data processing agreement (DPA)
An agreement specifying data-processing roles, instructions, security, and subprocessors.
Technical and organizational measures (TOMs)
Measures intended to protect data and services.
Security advisory
A versioned publication describing the exposure, impact, mitigation, and status of a product vulnerability.
GROUP 04

Evaluation and operations

6 definitions

End-user license agreement (EULA)
The agreement governing the end user’s rights to use the app.
Service-level agreement (SLA)
A contractual commitment to a service level and the conditions used to measure it.
Dry run
A controlled rehearsal of a migration or deployment before the real cutover.
Rollback
The procedure for returning to a safe state when a deployment or migration fails.
Known issue
A confirmed problem or limitation with documented scope, impact, workaround, and status.
Changelog
The record of shipped changes, distinct from a roadmap that describes non-guaranteed horizons.

A definition becomes useful when it changes the next question.

Move from the term to the evidence register: permission scopes to Security, retention to Data, and listings to Pricing.

Assemble the evidence pack