Hi Atlassian developers!
My name is Jakub Mierzewski, I am a Product Manager responsible for Jira/Forge extensibility. I want to share with you our plans and things recently shipped. The previous Jira extensibility update was posted in Aug 2021 and it is time for an update.
How to read it
Note
This is an update for the FY22 Q3 and Q4 which ends in Jun. Page was created on Mar 1, 2022.
Please keep in mind that plans may change as we always learn on the way. Jira/Forge extensibility related features are grouped in three categories new Forge-only Jira features, Forge connect modules equivalents and new APIs and Events.
Glossary
In progress - development is in progress and we plan to release at least the first version by June 2022
Next - we have decided to start work by June 2022, development haven’t been started we are in design phase, it is a great moment to include your feedback , not all features will be finally implemented
Candidates - we gather interest and believe that this is an important feature on which we may work in H2 2022
Share your interest
All incoming work is publicly visible and have a public ticket. If you are interested in a particular feature vote for it . Use comments to inform us about your use cases, specific requirements , strong opinions and questions. Your votes, questions and comments matter. When we are selecting candidates no. of votes and partners engaged is one of the most important criteria. I hope you like the fact that all incoming works is visible and we can start collaboration early.
Forge-only Jira features
Forge opens new extensibility areas . Be the first who covers not yet utilized use cases available only for Forge.
Done
- Custom fields object type
- Context configuration of custom fields
- Formatter support
- Enable custom UI in custom field edit entry point
- Forge custom fields on create issue view
- JQL editor module (available also for Connect)
- Datetime new Forge custom fields data type
In progress
- FRGE-608: Issue adjustments API
- FRGE-613: value function for custom fields
- FRGE-609: Forge custom fields inline edit on create issue view
- FRGE-85: Implement Workflow Conditions in Jira
- FRGE-177: Allow apps to navigate (or refresh) the browser
Next
-
FRGE-135: Forge Custom Fields on new issue navigator view and boards
in this ticket, we have an ongoing discussion whether it is enough to render Forge custom fields with Formatter and for what use cases UI kit support is needed. - FRGE-231: JQL function Forge extension point
Roadmap candidates (June 2022 +)
- FRGE-615: Forge in team managed projects
- FRGE-243: inline custom field edit
- FRGE-614: Live updates in Forge extensions
- FRGE-623: User Profile extensibility
Forge connect modules equivalents
We want to make Connect vs Forge decision easy. Share with you our plans early and enable you to build more and more apps with Forge. We have recently released 3 connect modules equivalents 5 are in progress, more is coming.
Done
In progress
- FRGE-158: Allow Forge apps to make entity properties searchable with JQL
- FRGE-207: Forge Dashboard Module
- FRGE-509: Multiple pages for a Forge app
- FRGE-494: Add Jira openCreateIssueDialog style bridge method to Custom UI
- FRGE-85: Implement Workflow Conditions in Jira
- JSM on Forge roadmap
Next
- FRGE-570: Workflow Validator - add support for configuration
- FRGE-638: Workflow post functions
- FRGE-582: Display Conditions using App property or Jira expression
- FRGE-617: jiraReports module
- FRGE-309: “Getting Started” postInstall page for Forge
- FRGE-618: configurePage module
Candidates (June 2022+)
- FRGE-622: Jira boards extensibility
- FRGE-620: jiraGlobalPermissions and jiraProjectPermissions Forge modules
- FRGE-619: Jira time tracking providers
- FRGE-472: Add support for Jira Software Cloud data providers (Open DevOps)
- FRGE-621: keyboardShortcuts Forge module
New Jira APIs and Events
APIs create a basic, fundamental layer of extensibility. Here’s how we plan to increase our API coverage.
Done
- APIs for Workflow management shipped with the support of Connect rules.
- APIs for Custom Fields delete and Custom Field context update.
- APIs for Gadgets in Jira (waiting for release)
- APIs for Filters management (waiting for release)
- ACJIRA-1986: No Worklogs in Issue for Jira Expressions
- The limit of the Webhook Trace Header size has been increased to 1024 characters.
- Custom fields related events
- OAuth 2.0 for all the JSW REST API endpoints
In progress
- APIs for Statuses in Jira
- APIs for Priorities and Resolutions
Next
- APIs for the new Workflow in Jira supporting both CMP and TMP workflows.
- APIs for Notification Schemes
- APIs for Issue Security Schemes
Further reading
- Forge Platform roadmap
- Bridging the gap between Connect and Custom UI
- Forge announcements
- Our ecosystem product team is presenting a live screening of the roadmap on March 7th, you can sign up here.