Make sure you understand these limitations before you start developing with Forge.
- Forge only supports sites that have both Jira and Confluence installed. The development site you
create in Getting started has both products by default.
- Your site must have a *.atlassian.net site name.
- You'll need to write your functions in a subset of Node.js. Some globals are not exposed, for
process (except for
queueMicrotask, which means that some NPM
packages will probably break.
- The following Node built-in modules are not supported:
- Functions have an execution timeout of 10 seconds. If your function takes longer than 10 seconds
to execute, it will be stopped.
- Some of the Confluence APIs do not support OAuth. On Confluence API documentation,
only the APIs with the OAuth scopes required entry can be called using
- You can install Forge apps in Jira and Confluence, but Forge UI only supports editor macros built for Confluence. We are bringing Forge UI to more places soon.
- Editor macros are only compatible with the Atlassian Editor. All cloud sites use the Atlassian Editor by default.
- Editor macros can only be inserted by typing "/" and selecting from the quick insert menu.
- Components ignore invalid props. Prop type validation with error messages is coming soon.
- Macro configuration has some known limitations:
- When you copy a macro, the configuration of the original or a copy may be overwritten. This
can happen when a macro is pasted and when the configuration of a copy is updated.
- When configuring a Forge macro immediately after configuring a Connect macro, the wrong configuration
form may be loaded.
- The option to edit the macro displays whether the macro has configuration or not. If the macro
doesn’t have configuration, nothing happens when a user selects edit.
Ready to start building?
Check out Getting started.