Modules are defined in the manifest, and they describe how Forge apps extend and interact with Atlassian apps.
Here are some examples of what you can do with Forge modules:
Some Forge modules remain in beta. While in beta, we may make changes that might break your apps. Learn more about the Forge deprecation policy, and what this means for functionality in beta.
Here's an example of how modules appear in the manifest.yml file.
1 2modules: macro: - key: hello-world-macro function: hello-world-macro-func title: Hello world macro! description: Inserts hello world! webtrigger: - key: webtrigger-sync function: my-forge-app-sync-func response: type: dynamic - key: my-webtrigger-async function: my-async-func response: type: dynamic trigger: - key: issue-creation-trigger events: - avi:jira:created:issue - avi:jira:updated:issue function: issue-trigger-func jira:workflowValidator: - key: my-forge-workflow-validator name: My example Forge workflow validator description: The description of my example Forge workflow validator function: my-forge-validator-function function: - key: my-forge-app-sync-func handler: index.runSync - key: my-async-func handler: index.runAsync - key: hello-world-macro-func handler: macro.run - key: issue-trigger-func handler: jira.issueCreationTrigger - key: my-forge-validator-function handler: index.runValidate
To learn more, check out the modules reference documentation.
Forge Dynamic Modules is now available as part of Forge’s Early Access Program (EAP). To start testing this, sign up here.
EAP features and APIs are unsupported, and subject to change without notice. Apps that use dynamic modules should not be deployed to production environments.
All dynamic modules created during EAP will not be carried over to Preview. For more details, see Forge EAP, Preview, and GA.
In addition to declaring modules in your app manifest, Forge apps can register some modules dynamically at runtime. This capability provides you with the flexibility to define an app's behaviour, and is useful for adding app features that are more responsive to arbitrary user needs.
Dynamic modules are registered in the context of an app installation, which means that an app can register different modules for each app installation. For now, only the Trigger module can be declared as a dynamic module. We are planning to add more in the future.
For more details, see Dynamic Modules.
You can only use these modules with Compass:
The ability to access UI extensions in Compass depends on your user role. Atlassian app admins can access all extensions, while full users can access some extensions. Basic users can't access any extensions in Compass.
The following modules can be used to extend the Confluence user interface.
The following modules can be used to run app functions in the background of Confluence.
You can only use these modules with Jira. You can also install the Forge Extension Point Finder for Jira on your site to interactively explore our modules.
You can only use these modules with Jira Service Management:
-->
Rate this page: