Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Just how much interest needs to be gathered before Atlassian considers a feature request?

The page you have to describe your process says that a feature that isn't ready to be triaged is in the state "Gathering Interest".  My question is what level of interest do you need to start looking at a request?

Is there a specific number of votes?  Set of comments?  Is 100 votes enough?  1000?

I ask this because there is a feature that would make my life a lot easier that has nearly 100 votes, but has been left untouched for years.  The feature would be relatively quick to implement, and is a missing feature of the markdown spec.

1 comment

It's not a simple "number of votes" - that is one factor, but there's also the support requests from customers that it might affect, the overall plan for developing the software, the new features that could be added, priority against other things, data coming from TAMs and integrators, and, and, and.

Everything you mentioned has to do with the decision process to include a request in a future release.  I understand the vetting process, what I'm asking is what is the threshold for a request to reach the vetting process?

How does a request go from a community request to at least be looked at for initial review by a member of the Atlassian development team?

I think you've missed my point - there's no simple threshold based on votes.

If you insist on a definition of "threshold", the best I can do is "it's in the backlog, and it contains words which may be of interest to the developers, product owners, integrators (internal and internal), TAMs, partners asking questions, and and and"

Atlassian support and development teams review new requests weekly, or even more frequently, but the sheer volume of backlog means they have to be very strict on refinement and what to draw in to both the sprints and long-term plan.  Jira Server's (public) backlog of stuff they don't want to shut down as "duplicate or going in the wrong direction" is almost 10k issues alone.


Log in or Sign up to comment
Community showcase
Published in Feedback & Announcements

The 2020 Content Awards

Happy New Year, Atlassian Community! In 2020 we all had to learn how to connect, share, and learn in an entirely different way. After a year of so much bad, we deserve to celebrate some good! The...

1,903 views 40 68
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you