3 ms·

Jira is extremely customisable. The "too complicated and enables a lot of processes and micro-management which used to kill our productivity" thing is a matter

by cess11 3y ago

Jira is extremely customisable. The "too complicated and enables a lot of processes and micro-management which used to kill our productivity" thing is a matter of management in the company, or whoever controls the implementation of project management flows, rather than Jira itself. I'm not a fan of Jira and avoid it if I can, but it has never reduced my overall "productivity", putting some text in some forms and clicking some buttons just isn't the kind of factor with such an influence in my experience.

mrweasel 3y ago
It's the same issue every time someone tries to brand themselves as an alternative to Jira. They implement 10/20% of the features, typically part of the task/bug-tracker and maybe the KANBAN boards and completely ignores the rest. The fact that products and startups feel the need to brand themselves as "Jira alternatives" says a lot about the absolute dominance of Jira in some markets. You're just not going to replace Jira with a minimalist bug tracker. If profit is your goal, you'd probably be better of reimplementing your AI feature as a Jira plugin.
- therealpygon 3y ago
  If there wasn’t a market for alternatives, people wouldn’t spend their time building them or marketing themselves as them.
  - cess11 3y ago
    How did you come to this conclusion? It's very common to develop software in response to dissatisfaction with social, organisational, issues. Issues that in turn are impervious to software incentives, that is.
sesm 3y ago
I think it's not about the Jira itself, it's about who manages it and power asymmetry it creates. If a bug tracker is configured by managers it will be optimized for manager productivity at the cost of developer productivity. Same thing often happens with infra/devops.
- cess11 3y ago
  Yeah, I mostly agree, I think it's often manager surveillance and control rather than productivity.
tiborsaas 3y ago
Can I customize it to select the epic and label on the ticket creation modal? I always have to click the link on the toast message to do these steps on a new screen, it's infuriating.
- cess11 3y ago
  Don't have an instance available to check, sorry. I've seen very simple setups that don't use epics and only have like three ticket types and a handful of states they can be in, like a basic kanban board, and very complex ones where several boards are interconnected and the flow is in part driven by integrations with CRM, git, CI/CD and Confluence. Most instances I've seen have been quite badly configured in relation to how the organisation prefers to work though, people get small cuts all the time and feel like they need to fight it daily.
  - tiborsaas 3y ago
    Sure, nobody cares to configure it "properly" whatever that means and I wonder if it's even possible. I'm also just an engineer in the team, I can't push through changes like this to abandon epics. I wish we should just set Jira on fire and switch to whatever else, but it's close to impossible when you have hundreds of engineers and PM-s using it. We're stuck with it probably forever.

by cess11 3y ago

mrweasel 3y ago

It's the same issue every time someone tries to brand themselves as an alternative to Jira. They implement 10/20% of the features, typically part of the task/bug-tracker and maybe the KANBAN boards and completely ignores the rest. The fact that products and startups feel the need to brand themselves as "Jira alternatives" says a lot about the absolute dominance of Jira in some markets. You're just not going to replace Jira with a minimalist bug tracker. If profit is your goal, you'd probably be better of reimplementing your AI feature as a Jira plugin.

therealpygon 3y ago
If there wasn’t a market for alternatives, people wouldn’t spend their time building them or marketing themselves as them.
- cess11 3y ago
  How did you come to this conclusion? It's very common to develop software in response to dissatisfaction with social, organisational, issues. Issues that in turn are impervious to software incentives, that is.

sesm 3y ago

I think it's not about the Jira itself, it's about who manages it and power asymmetry it creates. If a bug tracker is configured by managers it will be optimized for manager productivity at the cost of developer productivity. Same thing often happens with infra/devops.

cess11 3y ago
Yeah, I mostly agree, I think it's often manager surveillance and control rather than productivity.

tiborsaas 3y ago

Can I customize it to select the epic and label on the ticket creation modal? I always have to click the link on the toast message to do these steps on a new screen, it's infuriating.

cess11 3y ago
Don't have an instance available to check, sorry. I've seen very simple setups that don't use epics and only have like three ticket types and a handful of states they can be in, like a basic kanban board, and very complex ones where several boards are interconnected and the flow is in part driven by integrations with CRM, git, CI/CD and Confluence. Most instances I've seen have been quite badly configured in relation to how the organisation prefers to work though, people get small cuts all the time and feel like they need to fight it daily.
- tiborsaas 3y ago
  Sure, nobody cares to configure it "properly" whatever that means and I wonder if it's even possible. I'm also just an engineer in the team, I can't push through changes like this to abandon epics. I wish we should just set Jira on fire and switch to whatever else, but it's close to impossible when you have hundreds of engineers and PM-s using it. We're stuck with it probably forever.