You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Greetings @Jason Fingerhut (and anyone else with thoughts on this matter),
I was just reading your recent comments on JSDSERVER-1476 , and I have a small tangent I hope you will take up, but I felt that the issue comment thread itself was not the right place.
It seems to me the trend for Atlassian has been cloud-first and maybe eventually cloud-only. My employer emphatically does not want that. I have this fear that if the cloud votes are "inflated," Atlassian will feel emboldened to continue to diminish in priority, and then eventually starve out on-prem offerings. So while I am very sympathetic (or rather empathetic) to our cause and your proposal, for me, it seems in the long run to increase risk of a "worse fate", albeit one further in the future.
Perhaps my fears are misplaced. I'd be glad to hear your thoughts on it, and also I'd be glad to hear more of your own, or any other sympathetic customer's ideas on how to effectively persuade Atlassian to make it a priority and to deliver on (at least a few of) these long overdue features, for both on-prem and cloud offerings.