11–20 of 205 posts
I observe load times that remind me of the 90s sometimes using their cloud apps.
Incredible they are killing on-prem, but maybe it makes it harder to compare to the slow as molasses cloud offering that way?
At this point the decision has been made in our org to firewall their products off the internet and internal networks, and migrate to something else by 2024.
[1] https://hn.algolia.com/?q=atlassian
[2] https://confluence.atlassian.com/security/cve-2023-22515-pri...
Jira/Confluence are two products that have gotten markedly slower and slower over time and as they've moved into the cloud. I observe load times that remind me of the 90s sometimes using their cloud apps. Incredible they are killing on-prem, but maybe it makes it harder to compare to the slow as molasses cloud offering that way?
Jira/Confluence are two products that have gotten markedly slower and slower over time and as they've moved into the cloud. I observe load times that remind me of the 90s sometimes using their cloud apps. Incredible they are killing on-prem, but maybe it makes it harder to compare to the slow as molasses cloud offering that way?
I have the opposite experience; many if not most of the features have gotten faster as the features have expanded in capability
Yet I still cannot import anything like in the old editor (e.g. markdown), adding images in lists was added two years after forcing switching to the new editor and you still cannot continue numbered lists in another item line and have to start over.
Extensions exist to do this but these things should be standard in any editor.
Last year I was second guessing myself if migration to Gitlab EE from Jira, Bitbucket and Jenkins would be worth it, as it was a massive shift for my org. Maybe purchasing a DC version of Atlassian products would be a better alternative, but after short look into invoices and licensing it was decided to go forward with Gitlab. Still not a big fan of how stiff Yaml pipelines feel in Gitlab CI and that tickets for what…
If some information is not in GitLab Git and CI, it should be in GitLab Issues or (ugly) GitLab Wiki.
Those 4 words avoid a lot of problems. Including avoiding a proliferation of silo'd and leaked and lost information in numerous different SaaSes, apps/programs, and storage services that people will tend to do by default.
At this point, I feel Jira is like WordPress. It maybe slow and overbloated, but you can have absolutely any plugin and/or integration you can think of.