Atlassian takes feature requests for Jira, Confluence, Bitbucket and its other products in public, as Suggestions on jira.atlassian.com, where anyone signed in can vote. Every one of them, 179,402 filed between 2002 and 4 October 2026 across 49 products, was read on that day with its status, resolution, dates, votes and watchers.
17.1 percent were built. 37.4 percent were closed without being built, and 27.7 percent are still open, with a median age of three years and three months. More votes help, mostly by keeping a request from being turned down: 46.0 percent of suggestions with one to four votes were closed unbuilt, against 3.5 percent of those with a hundred or more. Being built takes longer. The median suggestion built with more than a thousand votes waited nine years.
key,project,product,status,resolution,created,resolved,votes,watchers
JRACLOUD-63150,JRACLOUD,Jira Platform Cloud,Closed,Fixed,2016-11-13,2023-06-22,8084,1455
JRACLOUD-4812,JRACLOUD,Jira Platform Cloud,Future Consideration,,2004-10-06,,2799,1176
BAM-883,BAM,Bamboo Data Center,Closed,Low Engagement,2007-02-16,2025-04-27,9,10
Download the file, one row per suggestion, compressed with gzip. It is free to copy, quote and use commercially. To cite it, link https://votefirst.app/en/data/atlassian-feature-requests and give the read date, 4 October 2026. Every key opens on Atlassian's tracker, so any row can be checked there.
How many Atlassian feature requests get built?
About one in six. A suggestion is counted as built when Atlassian closed it as Fixed, Done or Deployed, and as closed unbuilt when it closed it as Won't Fix, Won't Do, Low Engagement or Timed out.
| Outcome | Suggestions | Share |
|---|---|---|
| Built | 30,733 | 17.1% |
| Closed unbuilt | 67,134 | 37.4% |
| Still open | 49,752 | 27.7% |
| Closed for another reason | 31,783 | 17.7% |
The other reasons are mostly duplicates, 14,052, and suggestions answered rather than built, 8,392. The remaining open ones hold 1,074,456 of the 1,915,867 votes ever cast, 56.1 percent.
Do more votes get a feature built?
They get it built more often, and turned down far less often.
| Votes | Suggestions | Built | Built more than 30 days after filing | Closed unbuilt | Still open |
|---|---|---|---|---|---|
| None | 81,915 | 22.8% | 10.4% | 38.2% | 15.5% |
| 1 to 4 | 61,973 | 9.4% | 8.0% | 46.0% | 30.2% |
| 5 to 19 | 21,443 | 13.6% | 13.3% | 29.4% | 45.2% |
| 20 to 99 | 10,108 | 20.7% | 20.6% | 9.0% | 61.9% |
| 100 to 999 | 3,848 | 31.3% | 31.2% | 3.5% | 61.1% |
| 1,000 or more | 115 | 47.0% | 47.0% | 1.7% | 47.8% |
Suggestions with no votes at all look like an exception, and most of it is timing. Half of those built were closed within 24 days of being filed, and 29.6 percent within a week, before anyone had time to vote. Counting only what was built more than 30 days after filing, the share climbs with every step in votes, from 8.0 percent at one to four votes to 47.0 percent past a thousand.
Votes say less about whether a request is built than about whether it is refused. Past a hundred votes, a suggestion was closed unbuilt 3.5 percent of the time. It was still open 61.1 percent of the time.
Of the 1,000 most voted suggestions on the tracker, 385 were built, 33 were closed unbuilt and 565 are still open.
How long does a popular request wait?
Longer the more votes it has, because a request collects votes for as long as it waits.
| Votes | Median days from filing to built |
|---|---|
| None | 24 |
| 1 to 4 | 265 |
| 5 to 19 | 642 |
| 20 to 99 | 1,038 |
| 100 to 999 | 2,004 |
| 1,000 or more | 3,284 |
Two of the most voted show the range. A dark theme for Jira Cloud, JRACLOUD-63150, filed in November 2016, was closed as Fixed in June 2023 with 8,084 votes, the most on the tracker. Priorities per project, JRACLOUD-3821, filed in May 2004, was closed as Fixed in June 2024 with 5,631, twenty years later.
Of the 49,752 still open, the median was filed 1,186 days before the read. 36.6 percent are more than five years old and 15.7 percent more than ten.
What does Gathering Interest mean on Atlassian's tracker?
It is where a new suggestion waits for votes. Atlassian's own status help says a suggestion in Gathering Interest needs more votes and comments, from more distinct customer domains, before its team reviews it. The same help lists the statuses a suggestion can move to after that: Reviewing, Under Consideration, Future Consideration and Not Being Considered.
Almost every open suggestion is still in that first status: 45,849 of 49,752. Their median is two votes, and their median age 1,089 days. 1,867 of them have a hundred votes or more, and 18 have a thousand or more without having moved past it.
Which requests have waited longest with the most votes?
| Key | What it asks for | Filed | Votes | Status on 4 October 2026 |
|---|---|---|---|---|
| ID-240 | Merge Atlassian accounts into one, with secondary emails | June 2015 | 2,851 | In Progress |
| JRACLOUD-4812 | Default values for system fields | October 2004 | 2,799 | Future Consideration |
| JRASERVER-1391 | Rename groups after they are created | March 2003 | 2,626 | Under Consideration |
| JRACLOUD-85694 | Choose the fields shown on cards in team managed projects | November 2018 | 2,463 | Future Consideration |
| JRACLOUD-91595 | Milestones on basic roadmaps | March 2019 | 2,426 | Under Consideration |
| CLOUD-6498 | Automatic backups in the backup manager | April 2013 | 2,252 | Waiting for Release |
| JSWSERVER-9167 | Sum the estimates of sub tasks into the story | June 2013 | 1,993 | Future Consideration |
Atlassian's status help describes Future Consideration as a candidate for the longer term roadmap that will be reconsidered in a year. The tracker records a suggestion's current status, not when it entered it.
What happened to the suggestions closed in 2025?
Most of them went in one sweep: 8,750 of the 11,933 resolved that year. Between March and May 2025, Atlassian closed 8,319 suggestions as Low Engagement and 431 as Timed out, more of those two closures than in any other three months on the tracker. Its status help defines Low Engagement as low customer engagement and limited demand, measured by votes and watchers.
The 8,750 closed in those three months had a median of two votes and had been open a median of 2,306 days, a little over six years. 1,356 of them had ten votes or more, and the most voted had 105.
Which Atlassian products build the most of what is asked?
The ten products with the most suggestions, by what became of them.
| Product | Suggestions | Built | Closed unbuilt | Still open |
|---|---|---|---|---|
| Jira Platform Cloud | 27,926 | 8.4% | 58.7% | 20.3% |
| Jira Data Center | 25,494 | 17.7% | 46.3% | 19.6% |
| Confluence Data Center | 18,770 | 19.0% | 43.6% | 17.1% |
| Confluence Cloud | 17,824 | 9.8% | 49.5% | 24.4% |
| Bitbucket Cloud | 9,469 | 27.4% | 40.3% | 14.8% |
| Jira Service Management Cloud | 9,051 | 8.9% | 29.8% | 51.1% |
| Bamboo Data Center | 9,010 | 36.8% | 31.8% | 12.7% |
| Jira Software Data Center | 8,318 | 20.4% | 26.4% | 24.1% |
| Jira Cloud | 6,018 | 18.3% | 40.0% | 2.7% |
| Bitbucket Data Center | 5,892 | 16.8% | 18.1% | 29.6% |
The older the suggestion, the likelier it was built. A third of those filed in 2005 were built, 32.8 percent, against 12.2 percent of 2015's and 10.1 percent of 2020's, and 90.6 percent of 2025's are still open.
How do you suggest a feature to Atlassian?
Atlassian's policy page names three routes: Atlassian Community, jira.atlassian.com, and the feedback option inside its Cloud products. On jira.atlassian.com, filing a suggestion needs a login, and every ticket is public. Search the product's project first: 14,052 of the suggestions read here were closed as duplicates.
The same page says votes and comments help, and that decisions also weigh support tickets, product analytics and research. It also warns that, with the volume it receives, many suggestions will get no update or reply.
What does that mean for your own feature request board?
On a public tracker of 179,402 requests, votes mostly decided what was not turned down. They did not decide what was built soon. The typical request drew one vote, and a popular one waited years with its voters watching a status that rarely changed.
The same pattern holds on far smaller boards. On 634 public Canny and Featurebase boards, the median request held two votes and requests with three to nine votes were decided no more often than those with two or fewer. On JetBrains' public tracker, 149,466 feature requests show the same curve with a different habit: 32.2 percent built, 4.1 percent declined, and 36.7 percent still open a median of six years after filing.
What a board owner controls is the answer. On VoteFirst, Denied and Completed are columns on the board by default, so a refusal is shown rather than left open, and when a release includes a request, every voter who was signed in when they voted is emailed that release. Anonymous votes leave no address to write to. Taking requests into Jira is covered step by step on its own page, and VoteFirst has no Jira integration.
How was this read, and when does it change?
Atlassian's tracker answers its public search API without a sign in. Every issue of the type Suggestion was read on 4 October 2026, a thousand at a time in key order, at one request every three seconds, and the 179,402 rows hold 179,402 distinct keys. Each row keeps the key, the project, the product, the status, the resolution, the date filed, the date resolved, the vote count and the watcher count. Titles and comments were not kept.
Built means a resolution of Fixed, Done or Deployed. Closed unbuilt means Won't Fix, Won't Do, Low Engagement or Timed out. Still open means no resolution and a status other than Closed; 1,072 suggestions closed without a resolution are counted with the other reasons. A suggestion's votes are counted on the read date, so a request built years ago had its votes counted after it was built as well as before. The tracker does not show when each vote was cast.
The next read is due by 1 January 2027.
14 days, a card at signup, then $9 or $39 a month.