Introducing a new public roadmap for Forge

Forge Forge Announcements
,
1

September 2024 update:
The new Forge roadmap is now available here: Forge Roadmap.

See the Introducing the new Forge public roadmap post for more details.

Original post:
Hey everyone,

I’d like to introduce you to the Forge platform roadmap for developers. This Trello board is a brand new public roadmap we’re trialing, and it’s dedicated to our community of Forge builders, as well as anyone else who’s interested in the current and future projects roadmapped for the Forge platform (which likely includes you if you’re reading this).

What happened to the “Atlassian platform for developers - roadmap”?

It’s not going anywhere. However, based on feedback, we found that the current Atlassian platform for developers - roadmap is little too noisy and busy for those who are interested only in Forge. Given the growing number of both Forge developers and Forge projects, we’ve decided to create a dedicated space for Forge updates.

Over the coming weeks we’ll be keeping an eye out for feedback from you, and we’ll work to improve the roadmap experience. In the meantime we’ll start linking the new roadmap to Forge cards on the old one and eventually archive them.

As of now, the new roadmap is the most up-to-date source of information for Forge projects.

How often will the new roadmap be updated?

This roadmap is fully reviewed on a quarterly basis, but individual projects may get updated more frequently by their respective teams (which will usually happen if major changes occur).

Getting started

When visiting the board for the first time, please take a look through the About this roadmap column. Mainly make sure you read the README card which describes the board and details the 3 columns projects are separated into (Build, Operate, Shift).

Highlighting the disclaimers

We’ve linked this on the board in our Disclaimer Card, but to save you a click, here are some important things to know while using the board:

We want to build relationships based on transparency and clear communication, but we all know that a solid plan can change or even be canceled. We are hopeful that the following can shed some light on the future of the Forge platform, but it is important to understand that it is being shared for INFORMATIONAL PURPOSES ONLY , and not as a binding commitment. Please do not rely on this information in making business decisions because ultimately, the development, release, and timing of any products, features or functionality remains at the sole discretion of Atlassian, and is subject to change.

And that’s it

Please feel free to explore the new roadmap and leave us comments in this post. I’m hoping that it will give you a better view of the various projects we have going on for Forge and a peek into our plans for the coming quarters. As always, if you’d like to chat you can reach me on nnikolaevsky@atlassian.com or schedule a Zoom call via Calendly here.

Cheers,

Nir

19 Likes
2

Would it be possible to remove Forge tickets from the old roadmap since we have a dedicated board for it?

1 Like
3

Sweet, thanks for sharing this with us @Nir ! :slight_smile:

Maybe one small comment: as the target quarters on the cards seem to say FY22Qx, I suppose that stands for Atlassian’s fiscal year and not the actual quarter of a year? If that’s the case, it may be nice to add a card in the leftmost column explaining that concept. So that developers who aren’t too familiar with Atlassian’s FY calculus can learn/remember about it and do the translation in their mind properly. :slight_smile:

Cheers,
Sven

4 Likes
4

You’re talking about this roadmap, right? Trello

5

Thanks for the suggestion Sven, I’ve added more details about the financial years and quarter we use to track our projects, plus some info about the states (in the works, next, future, shipped) to the README card. Let me know what you think :slight_smile:

2 Likes
6

If you’re referring the roadmap @bentley linked (which is the one I referenced in the “What happened to the “Atlassian platform for developers - roadmap”?” section) then yes, I will first link the new roadmap to the old Forge cards (for people who missed this post but still track the old roadmap) and then after some time we’ll archive the cards.

As mentioned in the post, make sure you follow the new Forge roadmap for all your Forge roadmap needs :slight_smile:

1 Like
7

Looks great, thanks Nir! :slight_smile:

1 Like
8

Thanks for this. I just realised there’s no cards covering on-prem to cloud migrations ie integrating with JCMA and CCMA?

10

Hey @jbevan - We are aware and investigating how to support Forge with App migrations platform. We’ll update the roadmap once we have a better understanding of the work and can commit to a quarter. In the meantime, I’d love to understand use cases! Are you thinking about server to cloud migrations with apps that have a first cloud version on Forge or are these apps that already exist on cloud via Atlassian Connect that are coming to Forge soon or both?

2 Likes
11

Thanks @akassab we’re thinking about Server/DC to cloud migrations for apps that already exist as Connect apps. How will harmonization affect anything we’re currently built for migrations? If we build a Forge app to offer some functionality of an existing Connect app before we harmonize the Connect app, what are the possible integration paths?

12

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

15

To make sure you are all across this, let me share that the new Forge roadmap is now available here: Forge Roadmap.

See the Introducing the new Forge public roadmap post for more details.

Caterina

1 Like