21–30 of 224 posts
Earlier quoted context omitted.
If only it _was_ the case!
Sliding in here with the hot take, but Jira can actually be pretty good! Github is terrible at project management. The problem with Jira (or at least used to) is that it has so much complexities that let people make it overly complicated.
Earlier quoted context omitted.
I'm lost now when it comes to project / dev / story etc management tools. No idea what the best option is, any recommendations for tools developers will actually use or do you just need to do a custom integration with github issues?
I've long wished for a tool that (for git) what fossil has built in: issues stored in the repository, where developers can use their full range of tools to work on them locally. A few additional things would be required to make this work for less-technical team members, and you end up building some of your own workflow, but it means that E.G. you have options like "update the description of a ticket as part of the pu…
Earlier quoted context omitted.
I'm lost now when it comes to project / dev / story etc management tools. No idea what the best option is, any recommendations for tools developers will actually use or do you just need to do a custom integration with github issues?
I've long wished for a tool that (for git) what fossil has built in: issues stored in the repository, where developers can use their full range of tools to work on them locally. A few additional things would be required to make this work for less-technical team members, and you end up building some of your own workflow, but it means that E.G. you have options like "update the description of a ticket as part of the pu…
(I'm in a many-repo company that used to use the per-repo bugtracker built into Bitbucket and switched many years to Jira. Jira has its warts, but it's miles better for the project management level task of burning down to a release.)
Must admit my comment is spurred by the first few words but my god Dreamweaver was so good in the early 2000's. I actually got introduced to it in ICT lessons at high school. Oh Adobe. The memory of their software is so nostalgic. Don't get me started, I'll be talking about macromedia shockwave next...
It's how I got my professional start too. It's code editor and file management was pretty nice for the time.
But if I were still working there I would probably replace most of the sites - which were largely abstractions of forms and tables - with something like power apps instead.
Earlier quoted context omitted.
I switched from Jira to Linear and am very happy with it. Just the right mix of power, completeness, and customization, without any fussy fiddling. It’s also blazing fast.
We're running Monday. Has to be used by approx 60-80 users mix of dev / old school projects & support. I'll check out Linear. Been looking at Clubhouse too.
Earlier quoted context omitted.
I'm lost now when it comes to project / dev / story etc management tools. No idea what the best option is, any recommendations for tools developers will actually use or do you just need to do a custom integration with github issues?
I've long wished for a tool that (for git) what fossil has built in: issues stored in the repository, where developers can use their full range of tools to work on them locally. A few additional things would be required to make this work for less-technical team members, and you end up building some of your own workflow, but it means that E.G. you have options like "update the description of a ticket as part of the pu…
It's a losing battle between tool functionality and reporting abilities.
Earlier quoted context omitted.
>The problem with Jira (or at least used to) is that it has so much complexities that let people make it overly complicated. I actually really like this take, because a lot of the times it feels like a tool's complexity is from what it lets you do. I feel like if Jira was "dumber" (i.e., less feature "rich") it'd be so much better.
To be clear - you have to go in and actively make Jira worse to make it bad. If you stick to the modern defaults and don't add in additional workflows you'll be fine. It's certainly an indictment of Jira and it's technical legacy that it lets to make it bad.
However, sometimes your crappy 60 person company doesn't know what's best. If jira didn't have the ability to make it crap it would be a better product and people would update their processes or maybe just try not to smush existing ms CRM workflows into a tool for devs.
Earlier quoted context omitted.
We're running Monday. Has to be used by approx 60-80 users mix of dev / old school projects & support. I'll check out Linear. Been looking at Clubhouse too.
What's wrong with Monday?
Very DIY. You can build great workflows if you put the effort in. Brilliant reporting, main reason we adopted.
Clubhouse for example gives the agile structure (epics, stories etc) by default and you conform to it. Minimal setup effort. From a 'management' perspective I actually like monday, by the actual end users don't seem to like it.
Getting a true hierarchy and relationships requires similar thought to setting up a SQL DB. Powerful, but I don't think we have the resource to really build upon and support stuff.
> JIRA was replaced by GitHub issues This is absolutely... not the case. Sure, for some kinds of projects Github Issues might do, but for anything "real" Github's issue and project management is a serious regression. --- These tools are not replacing anything, but addressing broader and broader markets. They lower the barrier to entry and bring more people into the fold (perhaps at the expense at having a lower ceili…
Earlier quoted context omitted.
Sliding in here with the hot take, but Jira can actually be pretty good! Github is terrible at project management. The problem with Jira (or at least used to) is that it has so much complexities that let people make it overly complicated.
>The problem with Jira (or at least used to) is that it has so much complexities that let people make it overly complicated. I actually really like this take, because a lot of the times it feels like a tool's complexity is from what it lets you do. I feel like if Jira was "dumber" (i.e., less feature "rich") it'd be so much better.