602

When happy teams are an issue (programming.dev)

submitted 1 month ago by arendjr@programming.dev to c/programmer_humor@programming.dev

115 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] theyllneverfindmehere@lemmy.world 80 points 1 month ago

For those complaining about Jira... I used to be one of you. After changing jobs and using several alternatives, I am begging to be back on Jira. Manage Engine is currently the bane of my existence.

[-] expr@programming.dev 13 points 1 month ago

I also wonder if people complaining about Jira are still on Jira Server. Jira Cloud is a much nicer experience. Certainly not perfect, but I've yet to see an actual viable alternative (once worked someplace that tried to move all project management to Gitlab... 🤮).

[-] keyez@lemmy.world 3 points 1 month ago

I worked at a engineering focused contract where we moved all our project management to gitlab and it saved so much time for everyone. Only hard part was collating data up to management in a way they could understand but I was happy to spend a few hours every few months to do that than using jira in any capacity

[-] expr@programming.dev 1 points 1 month ago

I'm sure it's fine for small-scale usage, but overall it's extremely inflexible and doesn't really scale well at all. There's also a lot of very basic functionality that's straight up missing. For example, there's no way to have a global epic priority. You can rearrange epics in an epic board, but the ordering of the epics there is not persisted elsewhere. There were many, many other shortcomings we kept running into.

Oh, and after a lot of our tickets had been imported (which itself was a huge undertaking since the auto import tools are complete trash), it started to be very slow. It feels like a very unfinished, unpolished product.

We use Gitlab's CI/CD features extensively at my current job and it's very, very nice. That's what they are actually good at, not project management.