Modules are defined in the manifest, and they describe how Forge apps extend and interact with Atlassian products.
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 - key: my-webtrigger-async function: my-async-func 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.
You can only use these modules with Compass:
The ability to access UI extensions in Compass depends on your user role. Product admins can access all extensions, while full users can access some extensions. Basic users can't access any extensions in Compass.
You can only use these modules with Confluence:
You can only use these modules with Jira:
You can only use these modules with Jira Service Management:
Rate this page: