21–30 of 97 posts
Website: https://taiga.io/
Docker: https://github.com/kaleidos-ventures/taiga-docker
Docs: https://docs.taiga.io/
GitHub and GitLab workflows are much more convenient in my opinion. They were made with actual workers in mind: developers, QA, release managers, DevOps, etc. Jira, on the other hand, is purely manager's toy with all it's useless features that often stand in a way of daily routine. I never saw any developer who was happy about Jira.
I am the ultimate smart tech man at my company. Warned them about Jira. Warned them about M$/Sharepoint/Power Automate. Jira and New M$ services are at bait pricing. They will all be extortionary levels at some point. Kind of amazes me people are paying for inferior closed off services, but I imagine the people making the purchasing decisions are more concerned about which concert or sports game the sales person is t…
What would you recommend as Power Automate replacement?
A ton of automation tools out there.
GitHub and GitLab workflows are much more convenient in my opinion. They were made with actual workers in mind: developers, QA, release managers, DevOps, etc. Jira, on the other hand, is purely manager's toy with all it's useless features that often stand in a way of daily routine. I never saw any developer who was happy about Jira.
You can make it as useless and as powerful as you want. I have worked on many projects and developers loved it (no joke). But it was down to having it properly setup and using just the bare minimum that enabled to do work. What often happens, is that JIRA "experts" (usually incompetent PMs or Scrum masters) let JIRA dictate your workflow. That's where discontent arises. (No affiliation to Atlassian).
Not true for project management features like, for example, "velocity" measurements denominated in story points (unitless) over time (seconds). Management metrics bullshit seldom benefits a project. In feature-monster tools like JIRA you have to do a lot of work to un-feature a project and those features are still lurking.
GitHub and GitLab workflows are much more convenient in my opinion. They were made with actual workers in mind: developers, QA, release managers, DevOps, etc. Jira, on the other hand, is purely manager's toy with all it's useless features that often stand in a way of daily routine. I never saw any developer who was happy about Jira.
You can make it as useless and as powerful as you want. I have worked on many projects and developers loved it (no joke). But it was down to having it properly setup and using just the bare minimum that enabled to do work. What often happens, is that JIRA "experts" (usually incompetent PMs or Scrum masters) let JIRA dictate your workflow. That's where discontent arises. (No affiliation to Atlassian).
That doesn't fix the horrible UX, sluggishness, confusing options, forms that present a lot of useless fields but don't give you the option to present other, more useful ones, ... I could go on.
Jira is a terrible tool.
On September 18th Atlassian announced a new license model for Jira automation that severely limits automation for all but enterprise customers starting November 1st. Many customers will be forced to give up their automation or upgrade to expensive enterprise tiers. Since there is no enterprise tier for Jira Product Discovery customers using automation in this product don’t even have the option to pay more.
> Since there is no enterprise tier for Jira Product Discovery customers using automation in this product don’t even have the option to pay more. This one is fascinating. I get paywalling features. I get removing features. But just turning them off is unusual.
If you’re on their products I feel for you son, but if you’re starting out I’d avoid anything Atlassin infected.
Earlier quoted context omitted.
This is more or less my life as well. The "finisher argument" that gets rolled out is "product lifetime costs". It goes like this. Open Source Product A will always be your responsibility, which will take X hours off the team's time forever. Vendor Product B will be maintained from the vendor side, thus removing that wildcard of X. Ergo, over the "lifetime" of the product, B will have lower costs than A. Since this a…
Open Source project O will cost your team X hours of time to develop expertise in managing it. Enterprise product E will cost your team X hours of time to develop expertise. O requires install time. E either requires install time or integration time. When O breaks, it is likely that the community has already seen this problem and can provide suggestions via docs, mailing list archives, discussion fora, blogs... Your…
O will never invite anyone to anything.
This is the secret.
Its maintenance takes like 2 engineer days per year total, if that. Its initial setup with all the plugins ( of note are those for project management and release tracking) and integrations (e.g. git) took one engineer week if I remember correctly.
And it works just fine for 7 years now, to the point that the only advantage of Jira I see is a slightly fancier looking interface for the regular user. Whilst costing peanuts.
I even prefer the old school Mantis BT look and feel.
I've always been a champion of Trello and really don't want to be having to add cautionary notes about corporate sharks owning it, and functionality taken for granted being whipped away. Not cool.
Earlier quoted context omitted.
Nah. It works really good. Not garbage at all.
I couldn't agree less. It costs a fucking ton and does not enable us to find information well, document stuff properly, and don't get me started on the fucking opaque permission management.
Search is great