The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Shape the Future of Jira Extensibility – Let’s Talk!

Exciting times are ahead for Jira extensibility! As we shape our roadmap, we’d love to hear from Atlassian ecosystem partners about your experiences—challenges, hopes, and feature requests. Your insights are invaluable in ensuring we build a more powerful and flexible Jira for you. Let’s connect! Sign up to chat with me, Yousef Abusamak, the new PM lead for Jira extensibility, and help shape the future of our platform. 

1 comment

Comments for this post are closed

Community moderators have prevented the ability to post new comments.

Mathew Lederman
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 10, 2025

I would love to see Atlassian take responsibility when they make a change that breaks forge functionality. We have a bug (ECO-582) that's been causing problems for our enterprise change management process for nearly 3 months. 

I'm cautioning our entire user-base to avoid Jira extensibility because Atlassian simply doesn't take responsibility to fix it's own issues. Apparently Forge is outside the enterprise SLA's, so it doesn't matter.

Like __ Jimi Wikman likes this
TAGS
AUG Leaders

Atlassian Community Events