The Atlassian developer documentation glossary.
| app | Supplemental software built to enhance Atlassian products. Can be distributed or sold through the Atlassian Marketplace. |
| Anonymous user | A user who is not logged in to an Atlassian account. |
| App lifecycle event | Event which is triggered in response to an app being installed, upgraded, or uninstalled. |
| App owner | Type of contributor that owns an app and has permissions to delete the app or change ownership. |
| Atlassian account ID | A unique value used to identify an Atlassian cloud user. The format is a case-sensitive string of at most 128 ASCII characters. |
| Atlassian Connect | A framework for building apps for Atlassian cloud products. Connect apps are hosted by developers or third-party hosting services. To build node.js apps hosted by Atlassian , use Forge. |
| Atlassian Connect Express (ACE) | An officially supported Node.js framework that generates some of the parts required for a Connect app. See also Atlassian Connect and Atlassian Connect Springboot. To build node.js apps hosted by Atlassian, use Forge. |
| Atlassian Connect Springboot | An officially supported Java framework that generates some of the parts required for a Connect app. See also Atlassian Connect and Atlassian Connect Express. |
| Atlassian Marketplace | The online store to buy and sell apps for Atlassian products. |
| Atlassian Plugin SDK | A development kit for creating, installing, and building Plugins2 (P2) apps for Atlassian Data Center products. See also Plugins2 (P2). |
| Atlassian Resource Identifier (ARI) | An Atlassian Resource Identifier (ARI) is a globally unique identifier used across Atlassian products and services for the unique identification of content. |
| Automatic update | An update to an app that is rapplied automatically to all installed copies of the app. |
| Cloud ID | A unique identifier for an Atlassian domain. |
| Confluence Query Language (CQL) | Confluence Query Language allows you to use structured queries to search for content in Confluence using the REST API. |
| Container | An entity within a product that provides structure and organization for objects. For example, within Jira a project is a container and within Confluence a space is a container. |
| Contributor | An individual that has a particular role which gives them permission to collaborate on the development and management of an app |
| Cross Product app | Apps that work across more than one Atlassian product. |
| Custom UI | An option for defining app interfaces on Forge using static resources, such as HTML, CSS, JavaScript, and images. The Forge platform hosts your static resources, enabling your app to display custom UI on Atlassian products. See also Forge and UI Kit. |
| Data security policy | All the things that an admin can do to manage security on their site; these can interact with an app in unexpected ways if not planned for during app design and implementation. Realistically, this needs some discussion to scope it properly. It is probably NOT "All" the things, but just some of them that are officially considered "data security policy". For example, app access rules are considered part of it. |
| Developer console | The Atlassian developer console is a platform for developers to create, manage, and integrate apps with Atlassian products. It offers tools for app management, API access, testing, distribution, and observability. |
| Entry point | Any action that invokes the extension point, such as a frontend interaction or a backend action. |
| Event consumer | A type of Forge module that reads or consumes events from an app defined queue. Alternative term: Async event consumer |
| Extension | An instance of an extension point - a specific implementation by an app using the extension point. |
| Extension point | An aspect of a platform or product experience that is extensible, including as part of the UI, a background task, or any other aspect of a product user flow. |
| Extension point chrome | The UI that is inherently part of the extension point and is visible on the screen. |
| Extension point component | A special Forge UI component that maps to a corresponding extension point and can only be used there. Will likely render a UI onto the screen. For example, the macro extension point expects the <EditorMacro/> component. |
| Extension point trigger | This is the “starting point” for an extension, which will fire an event that eventually leads to invokeExtension being called (either directly or indirectly). It can be both frontend or backend. On the frontend, these are the places where UI will be injected (not necessarily Forge UI), potentially in addition to the extension point itself. For example, the EditorMacro extension point registers 3 trigger points: the /-command, the add-new menu, and the macro browser. On the backend, these are the events which require a Forge response, usually in response to actions within the Atlassian system, e.g., product triggers. |
| First-party app | An app written and maintained by Atlassian. See also System app. |
| First-party Party | Atlassian and/or its developers (including contractors). |
| Forge | The app development platform used to customize, extend, and integrate Atlassian cloud products. Forge apps are hosted by Atlassian. |
| Forge CLI | A command-line tool used to develop and deploy Forge apps. See also Forge. |
| Installation ID | A unique identifier for every installation of an app. |
| Invocation count | Total number of invocations of a given Forge app over a given period of time. |
| Invocation errors | Total number of failed invocations of a given Forge app over a given period of time.
Alternative term: Function errors (deprecated) |
| Invocation success rate | Percentage of successful invocations of a given Forge app over a given period of time. Shown within the developer console. |
| Invocation time | The time it takes for each function to complete an invocation. In the dev console, a graph shows the distribution of invocation time across individual functions. |
| Jira Cloud platform | A platform that provides a set of base functionality shared across all Jira products, such as issues, workflows, and more. Jira products including Jira Software and Jira Service Management are built on top of the Jira Cloud platform. |
| Jira Query Language (JQL) | Jira Query Language is a tool for building structured queries to search for issues. |
| List app | Share app on Marketplace. Alternative term: publish app |
| Log access | Developers can access customer logs for their forge apps. The access is controlled by the customer admin through admin.atlassian.com and they can disable this at any time. |
| Major version change | An app change that will require an admin to update the installed app. In the case of forge apps, there are certain scenarios in which a major version change may result in end users being prompted for consent. |
| Manifest | A configuration file for the Forge app that defines properties of the app such as app id, name, scopes, and modules. |
| Marketplace Partner | A person or company that sells or distributes apps and integrations in the Atlassian Marketplace. Formerly known as vendor. |
| Minor version change | An app change that is released automatically to users. Alternative term: Admin approved update |
| Module | An entry in the manifest to use a capability from Forge or the product. Will often refer to a product extension point (UI or not), e.g., editor macro or product trigger, and it can also refer to a Forge platform capability, e.g., external OAuth. |
| Organization | A centralized place for an admin to manage Atlassian products, billing, and users, sometimes spanning multiple cloud sites. See also Site. |
| Plugin | See app. Used only in the context of apps built with P2. |
| Plugins2 (P2) | A framework for building apps for Atlassian Data Center products. |
| Private app | A private app is a custom application developed for specific use-cases within an organization, these apps are not publicly listed on Marketplace. |
| Prop (property) | Value that is passed to a Forge UI / JSX component. They're usually used to influence how the component renders or to wire it up to other components. Values can be data, content, or a function. For example, <MyComponent myProperty="Value of property" otherProperty={{ myFunc }}/>.
Alternative term: Property |
| Public (app) | An app that is listed on the Atlassian Marketplace. |
| Role | A group of permissions that gives a level of access to build and manage an app (Owner, Admin, Viewer etc). |
| Scheduled Trigger | A type of Forge module that repeatedly invokes a function on a scheduled interval. |
| Scope (permissions for Forge apps) | Scopes enable an app to request a level of access to an Atlassian product or to a particular feature or html functionality within the product. |
| Second-party app | Apps that are built by external developers, and use the Atlassian developer platform to build the apps. |
| Share app | Make app available for distribution. Developers can share an app via Developer console or Marketplace depending on the intended audience. Alternative term: distribute app |
| Site | A suite of Atlassian cloud products at a unique domain, typically ending in atlassian.net. A site contains a single instance of each product you're using, which may include Confluence and each Jira product (Jira and Jira Service Desk). See also Organization. |
| System app | System apps are installed along with the product. They cannot be uninstalled or managed by the admin. |
| Trigger | A type of Forge module that invokes a function or endpoint when a product event is fired. |
| UI Kit | An option for building dynamic and interactive app interfaces on Forge, using declarative markup language and built-in Atlassian components based on the Atlassian Design System. See also Forge and custom UI. |
| Unlicensed user | Users who have Atlassian accounts but do not have a product license on a specific site, for example, they might be licensed in Jira Software (JSW) and Confluence but not in Jira Service Management (JSM). |
| User tier | The maximum number of users that are enabled to use the product based on the current billing plan. |
| View | Any rendering of an app at a UI location, from an app onto the screen with any given extension point. A single extension point can have multiple views, depending on the context such as a modal. |
| Web trigger | A type of Forge module that invokes a function as the result of an HTTP request. |
Rate this page: