nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How we're shaping the future of the Atlassian Community, together 💙

Monique vdB

Hello, community! 👋

With our brand-new platform up and running, we want to make sure your voice directly shapes how our community evolves. That’s where our Forums Ideas & Feature Requests space comes in!

Whether you’re submitting an idea, chiming in on a thread, or casting your vote, here’s a quick guide to how the ideation process works and what each status means.

🗳️ How Ideation works

Submit & discuss: Community Champions can submit new ideas and feature requests. (Not a Champion yet? Share an idea in the comments for Champion consideration.)
Vote: Browse the board and upvote the features and improvements you want to see most.
Review: We regularly review top-voted ideas with our development, design, and platform teams to evaluate feasibility and provide transparent status updates. Subscribe to the community-release-notes tag to get regular updates of what is releasing and what is coming up next.

🚦 What the statuses mean

Every idea goes through a lifecycle so you always know where things stand:

Gathering Feedback: The idea is open for community discussion, feedback, and voting. Dive in and make your voice heard!
Under Consideration: The idea has gained significant community traction and is being actively reviewed by the community and product teams for feasibility, scope, and priority. You can expect this to happen once the idea has more than 20 votes.
In Progress: Good news! The idea is approved and actively being built or configured by our team. You can expect monthly status updates on In Progress ideas.
Requested from Vendor: Some features depend directly on our platform vendor. When this happens, we’ve formally logged and advocated for the request on their product roadmap. You can expect quarterly status updates on RfV ideas.
In Backlog: This requires engineering or design work and prioritization, but is in our backlog for future delivery. You can expect quarterly status updates on Backlogged ideas.
Delivered: It’s live on the forums! 🎉 Thank you for helping us bring it to life.
Closed (Won’t Do): While we wish we could build everything, some ideas may not be technically feasible or align with our long-term roadmap – or, they could be duplicates of existing ideas. Whenever an idea is closed, we’ll do our best to share the rationale behind the decision. If an idea has not gotten 10 votes over the course of a quarter, it may be closed for lack of community demand.

🙌 Ready to share your thoughts?

Head over to the Forums Ideas & Feature Requests space to explore current ideas, cast your votes, or drop a comment.

We can't wait to see what you’d like to build together next! 💙

Comments

That's so good!

Thanks Shane!!

Love to see this!

I already told the Community team in Amsterdam that you've opened Pandora's box with this one! 😅 I'm full of ideas, and I still have an entire Confluence page of suggestions waiting to be "migrated" to the new Ideas & Feature Requests space.

Steph said, "Go for it!" so… good luck to everyone on the Forums team! 😂

Jokes aside, I really like this concept! 💙

~~One thing worth considering for the long-term backlog is automatically suggesting existing ideas to prevent duplicates...~~

Never mind, I just created a separate idea for that! 😅 Suggest similar ideas before submission

Huwen Arnone [ACE]

Thank you very much! I'm not like @Tomislav Tobijas with a huge backlog of ideas, just one, I promise.

Well, maybe two. Or three. But just that. Thank you @Monique vdB 😎

Dave LIAO

Love that the suggestions for the forums are embedded in the forums. So cool, and way better than a Trello board…

I wonder if there are any suggestions from that old board that would apply to our shiny new environment… 🤔

Hugo Mora

Hi Monique,

Thanks for laying out the statuses — the part I appreciate most is that Closed (Won't Do) comes with a stated rationale. Most ideation boards quietly let things rot, and "no, because X" is far more respectful of people's time than permanent silence.

Two bits of friction worth thinking about:

The non-Champion path isn't a loop. If I comment an idea for Champion consideration, I don't know if anyone picked it up, who decides, or how long to wait. A note on the idea's thread when a Champion adopts one would close that circle cheaply.

Vote thresholds reward visibility, not merit. 10 votes in a quarter to survive and 20 to reach Under Consideration are reachable numbers, but whether an idea hits them depends mostly on where it lands on the board and who happened to be browsing. An idea submitted three weeks before quarter end gets a much shorter runway than one submitted in week one. Is the quarter counted from submission date, or on a fixed calendar?

Either way, glad the statuses are public. Off to go and vote.

George Villagaray

I don’t know - Atlassian has been ignoring its users request to stop spamming us with ads, sending bad UI updates to our sites without warning, and shilling AI tools we don’t want. This felt like a way to hide all the bad comments and press and “hide the issue”.

Jeff Parla

George that's a great point!

Why is there ANOTHER place to put in feature requests? There's already a Jira site! https://jira.atlassian.com/browse/JRACLOUD-80451

Dividing the community across different sites is a great way to dodge accountability.

Shivam Kadwade

This is helpful and will definitely shape community for the best!! 😎

Thanks Monique. This is actually great, I'm heading there for sharing my ideas…

Monique vdB

Thanks for your feedback! I think I incorporated all of it :) ⭐️

Monique vdB

The quarter is counted from the submission date. :)

Monique vdB

@Jeff Parla and @George Villagaray This is not for product feature requests - this is just for the community itself. We've never had a place for official feature requests other than a private Trello board for Champions. And the workflow is deliberately designed for transparency and accountability and will be managed by me and my team personally. I hope that helps!

Jeff Parla

Sounds good! This is already nicer than the product one anyways.
Downvotes would help too - upvote only means negative feedback isn't taken into consideration which is terrible when it comes to gauging feedback!

Hugo Mora

Perfect, that's cleaner than I assumed — equal runway for everyone. Thanks for clarifying. The other one still stands though: any plan to let people know when a Champion picks up an idea they suggested in the comments?

George Villagaray

I think this will cloud priority and allow Jira products team to ignore system deficiencies as the community creates workarounds for the deficits.

Monique vdB

I imagine the Champion would reply to the comment with a link to the idea!

Monique vdB

For now you can put your negative feedback in a comment and we will read it. I can also create an Idea to allow people to downvote Ideas…. (meta).

Monique vdB

My team doesn't work on Jira or on any of our products, we just manage the forum. If you have product feedback, there are other avenues for that - but if there's something specific you're wanting an update on I will see what I can do!

[A9] William Kennedy

If you want some tools to extract customer sentiment and feature signals from Atlassian Community Q&A posts, I have 'em.

Welcome!

It looks like you're new here. Sign in or register to get started.