I hear the frustrations, and have lived with many of them for a long while. The use of a group name instead of a unique id was a mistake right at the start and I wish it had been fixed at the same time that changing user names was added. Perhaps one day it will be, but in the Cloud, unlikely Data Center. I think it's time to close this as Won't Fix. 

p.s. As of January 2025 Atlassian has not been purchased and one of the founders remains. 

We have just moved out of Jira, mainly for the continuous cost increase and an internal competition in our company with ServiceNow (which is not as good as Jira from dev UX and customization perspective). But i can totally relate to what you said. I guess technical debt won't be handled better now that Atlassian has been purchased and initial founders are gone...

We still use Confluence, but also considering moving. We're starting to look into Notion, but it's more expensive than Confluence...

Solutions to generate static web pages from markdown or code, such as Github pages can be a good and unexpensive option for developers. Or opensource CMS / wiki.

PS for Atlassian support: as this issue is likely not going to be fixed, can we rename this thread "Anger for Atlassian, how to quit?"

1e260c3d59e9 we have found great success and cost savings with Microsoft DevOps Boards for Jira replacement. It's also practically free for most users that just need read-only or simple task management. Far more robust support for Agile, no need for the bolt-on Plans which I have always hated. Github Intergration actually works properly too. Good API support to fill in any automation gaps.

On the Confluence side, we moved to Confluence Cloud, we are happy enough with it except for its cost. We keep looking at alternatives, but they are all expensive too. My issues with Jira are foundational to its architecture, while if I had the Infinity Gauntlet I would snap my fingers and remove all Java-based apps from this world, Confluence for the most part is worth saving. It has administrative tech debt for sure, but it’s also truly the best product in its vertical, the same definitely cannot be said for Jira. 

Labels: TBC admin-at-scale affects-cloud affects-server jira_support_feature_request_emea jw-platform pse-request spam

If anything I feel special knowing that this is the ONLY issue that has label "spam"(~April 2023).
I wonder what that does and/or implies.

Someone perhaps cloned this one into JRASERVER-72769 by mistake?
Personally I can't say issue type suggestion sounds right, on the other hand Jira likely never had the feature so it depends on perspective.

//Tomas

Hi Eric,
I totally agree with U. The Licenses, the Users, the Permissions are horrible to administer on Atlassian products. Such a big potential wasted. I would be interest to know what platform you are migrating to? I also start to look at this but I want something similar to Jira/Confluence with capabilities like ScriptRunner offers (in platform dev), workflows, issuetypes creation, with established extensions market, etc. I would also love to have better control over particular "issues" as Jira's per project granularity for all permissions and Issue level security is not enough. You could say I am looking for Jira+Confluence on prem but better. 
Cheers!

P.S. Geographically displaced disaster recovery direct support would be also welcome. Well, I think I am getting dreamy... 

Guys I am totally with you. Especially every year price increase for nothing. But I am not sure, if there is somebody watching this issue because of "spam" label. You should contact Atlassian sales directly to express your feelings. 

Totally agree with Eric. 

I have to express my growing frustration with the level of support provided to Jira administrators. Despite the constant price increases year after year, it feels like our requests are simply not a priority. Critical issues and long-standing bugs remain unresolved for years, while new features keep rolling out that often don’t address the real pain points for those managing the platform.

It’s disappointing to see Atlassian focusing more on pricing than on actually improving the experience for admins who have to keep these systems running. I hope you start listening to administrators and prioritizing long-overdue fixes.

8f4f3c407f2b: Just for clarity: What do you mean by "Service now seems to be a way better option for us, [...]"?

98aa6e9bc70b  I totally feel for you mate. 
Even though I personally enjoy the product, its those stupid limitations that push you to check other vendors. Also the continuous increase on prices and limited updates on DC, create the need to check other providers.
We have been using Jira for over a decade now and we seriously consider moving to another platform instead of migrating to cloud. 
Service now seems to be a way better option for us, all things considered.   

This has been open since 2003. The idea that you don't use object GUIDs to store permissions is mind-blowing for 2003, let alone 20+ years later. I can respect how much work it would be to do this right, but I just wanted to take a jab at you for a moment. Why take a jab? Because your decades of tech debt on stuff like this burdens me, the admin. It has for so many years. It’s not just this foundational mistake; it’s all of them. Your foundation is trash, and you have never taken the time to fix it. Moving to the cloud hasn’t made things much better, in many ways worse given the lack of quality API access. At least on-prem, I can edit the db directly to work around your tech debt. 

 I don’t know who needs to hear this at Atlassian, but stuff like this… stuff like this is why I, as the admin of all things Atlassian, am begging my developers to move onto other platforms. I truly hate having to admin your platforms. So many things just like this, ignored and not fixed because the end users don't see it. Well, I see you, and what you’re not doing, it will cost you my company’s continued spends. Each year, I get a few more Jira projects over to other platforms. Once we are off, we will never be back, and it’s because of stuff like this.