4 ms·
> JIRA cloud was unusably slow and as a result we didn’t want to use the tool. We hated it even though it technically “worked”. - every JIRA customer ever
by ryanisnan 6y ago
> JIRA cloud was unusably slow and as a result we didn’t want to use the tool. We hated it even though it technically “worked”.
- every JIRA customer ever
- magicalhippo 6y agoWe're a JIRA customer and we're quite happy. It's not slow, at least to any degree that matters. We're not a huge team, nor do use much more than tickets with FishEye integration though. We also have a self-hosted instance. But for us it has worked quite well, and I have better memories of JIRA than say MantisBT which I used before.
- ithkuil 6y agoCloud or self-hosted?
- magicalhippo 6y agoSelf-hosted, as mentioned.
- p_l 6y agoA lot of issues can be mitigated when you self host vs using JIRA Cloud, not just because you might have beefier hw and better network link. While I suspect it got better, periodic reindexing and similar cron jobs were a hell on a team separated by 9 hour timezone difference, because time chosen for convenience in San Francisco meant many Mondays of "Atlassian Cloud is down" for team in Warsaw.
- magicalhippo 6y agoWow, that sounds horrible. While we're all in the same timezone in our company, we're also programmers... so that doesn't always matter. I've been using our JIRA in the middle of the night on several times, and it's just... there. edit: so yeah just highlights the self-hosting vs cloud...
- munchkinship 6y agoyou are self-hosted, which is different from cloud.
- magicalhippo 6y agoBut we're still JIRA customers, which was the point I was trying to make.
- m_eiman 6y agoSame here - went from MantisDB to Jira and it's a big improvement in so many ways.