3 ms·
I'm in a Very Large Company that just yoinked Jira and replaced it with GitLab Issues. I can't even tell how badly it's going because no-one knows what going o
by verytrivial 3y ago
I'm in a Very Large Company that just yoinked Jira and replaced it with GitLab Issues. I can't even tell how badly it's going because no-one knows what going on with any project now. People are literally copying and pasting hand-edited Excel summaries of sub-projects in emails and asking people to edit in place and reply. It's hilarious.
It's super standardised, though.
- dathinab 3y agodo you think it's an issue of gitlab or of the transition? As far I know Jira and GitLab issues initially can look kinda similar (depending on how Jira is used) but are very different in what works well with them so Jira to GitLab transition seems rather risky. And while I haven't used GitLab issues a lot, GitHub issues are kinda terrible and Jira isn't better either (but bad in different ways; with github actions you can try to "fix" GitHub but in practice this doesn't work that well my experience and can't fix the most important issues)
- verytrivial 3y agoGitLab Issues, especially as exposed by the UI is just ludicrisouly primitive vs Jira. They're trying to cover the GitHub use case regarding basically 'context for merge requests'. There's no planning, reporting, sane linking, reports, no query language, no batch updates, and visibility model means Issues edits are also basically committers, so good-bye segregation. It's just chalk and cheese. Someone invariably says 'with the REST API you can do ...' which now means we have hundreds of teams reimplementing the out-of-the-box Jira features in mutually incompatible ways for their own consumption. All of that dev time is gone. I honestly hope the shareholders don't find out.