Rate this page:
While the Forge platform is generally available, some functionality will remain in beta. While in beta, we may make changes to such functionality. Some of these updates might break your apps, but we'll provide advance notice when we release breaking changes. These breaking changes won't follow the regular six-month Forge deprecation policy.
Be among the first to try the following functionality in beta.
The UI kit is designed for Forge apps with simpler user cases. The UI kit lets you easily build intuitive and familiar interfaces by composing built-in Atlassian components. Hooks and event handlers enable UI kit apps to handle user interactions and return views dynamically from the server, where the UI kit code is executed. Learn more about the UI kit.
This module lets you create a new custom field in Jira, which makes it easier for users to add information to issues, specific to their teams' needs. Learn more about the Jira custom field module.
This module lets you create a new custom field type in Jira, which lets Jira administrators create new custom fields based on that type. Learn more about the Jira custom field type module.
This module creates a workflow validator that can be configured on workflow transitions in company-managed projects. Learn more about the Jira workflow validator module.
This module invokes a function on a scheduled trigger at a specified interval, either hourly, daily or weekly. Each schedule starts shortly after the app's deployment. While you may not see an invocation of a scheduled trigger immediately after deployment, it will invoke once within each interval specified for that trigger. Learn more about the scheduled trigger module.
This module invokes a function as the result of an HTTP request. To obtain a URL to call a web trigger, first define a module, and then run in the Forge CLI.
Note that while in beta, web triggers only work for the developer of the app. Learn more about the web trigger module.
Rate this page: