341–350 of 539 posts
Single letter hotkeys are pretty bad. If it's not an input field you've focused but the page itself, you might assign the ticket to yourself and set it to some crazy state before you realize the focus is all wrong. Ask me how I know...
Earlier quoted context omitted.
> You mean as hard as when Git obliterated every other VCS within the span of a few years There's not a concept impedance mismatch going from CVS->SVN->GIT. The concepts are so similar that git-svn exists to convert a SVN repo into a git repo (and a similar conversion tool exists for CVS->SVN) Jira is so flexible and configurable that no such tool could exist. Migrating to a new tracking system requires that you eith…
How about when every single company rewrote their frontend stack in React after angular.js was done, circa 2015? Or when everyone moved to k8s within 2 years around 2017-2019? Hell, now even companies that definitely wouldn't benefit from anything related to k8s are diving into it. What I am trying to show by these examples is that things can move fast, very fast, and that in our industry there are no such thing as w…
God I wish that were the case. My company is still rocking Angular unfortunately :(
> Or when everyone moved to k8s within 2 years around 2017-2019
That did not happen. k8s got a good share of the market, but it's far from "everyone moved".
> What I am trying to show by these examples is that things can move fast, very fast, and that in our industry there are no such thing as well-entrenched tools.
The tools you are listing are all dev tools picked, used, and curated by development. Jira isn't a dev tool, it's a product management tool. There's a major difference between tools that devs can pick and choose and tools that an organization gets to pick and choose.
Even with your "yarn" example, while it took over it didn't replace "npmjs" as the centralized repository server. Just like gradle still gets it's artifacts primarily from maven central.
I'll go back to something I said elsewhere. If it's so easy to move and change why is C++ still being written? Why does it remain one of the most popular programming languages even though most people are VERY quick to point out it's major flaws. Even though other better alternatives exist (Rust, Nim, D, etc).
> losing issue history is far less damaging than it was losing "commit" history when everyone was moving to git back in the days.
Assuming you like everyone else went from svn->git I don't see how you'd have lost commit history. I personally converted a BUNCH of repos to git and didn't see any cases of lost history.
Earlier quoted context omitted.
>If a company is trying to use JIRA for more than state communication they are doing it wrong IMO. This is why tools that don't allow this kind of doing-it-wrong are significantly superior to Jira.
That's a nice theory, but in practise people have been mailing to Slack, using meetings to read emails and using JIRA to track Git commits. Tools are just slaves to reality, not the other way around. If a legacy top-down organisation wants you do to a certain thing a certain way, and you have no recourse but to do as you're told, that's your organisation's fault and nothing else. You can either gain a position where…
That's naive; tools influence the way they're used. When a tool defaults to having manager accounts that can change how things get done and developer accounts that can't, it nudges the organisation in that direction.
I feel like hating on Jira is the pastime that is now passed down from each generation of programmers to the next. I'm going to stick up for Jira. I certainly don't "love" Jira, though I do think they've made significant improvements with "new Jira" (I think they call them team-managed projects now). The problem I have with the incessant Jira bitching is that I rarely feel that bitchers have a true understanding for…
It worked flawlessly — in fact I haven't been at a place that was as well organized since. And it all came down to one thing: everybody understood that there is only email and that if it isn't an email it will be forgotten and fall in some crack, so you better make it an email, that has a propper subject, is searchable, etc. That meant everybody was writing emails with nearly military rigour, while the asynchronous nature of the electronic letter always reminded you, that you just needed your emails done and then you were fine. Depending on your position you had multiple (shared) inboxes that corresponded to the tasks. Of course there were some old emails, that were more of a "if anybody finds the time and will" type and sometimes emails from the guy from the day before had to be done etc. But all in all it was surprisingly pleasant to work just with email.
The point of the story is: You can turn any tool to shit if people use it in a bad way. And you can make anything work if people use it in the right way. Most problems with communications are people-problems, not tool-problems. Sure certain tools may lend themselves to certain behavior more than to others but ultimately a team can decide how they wanna communicate effectively and which behavior produces chaos and problems.
I feel like hating on Jira is the pastime that is now passed down from each generation of programmers to the next. I'm going to stick up for Jira. I certainly don't "love" Jira, though I do think they've made significant improvements with "new Jira" (I think they call them team-managed projects now). The problem I have with the incessant Jira bitching is that I rarely feel that bitchers have a true understanding for…
I was asked during a merger, which work management tool do you think we should keep/use? I replied, don't ask me, I'll hate it anyways. It's not because I hate Agile, Scrum, or even Waterfall (although I do hate SAFe). I just know these tools all suffer from similar drawbacks, and somebody will ultimately codify all our organizational problems into the tool. Then, rather than spend an hour a week of their own time, t…
I wish the comments were more specific about which features they don’t like. For me a particularly frustrating aspect is the way the UI moves around a lot. I’m quite anxious to click anything until all the loading spinners have stopped in case I click the wrong thing. Then I could be taken to a page or feature I’ve never seen before. Also it’s really annoying when I try to copy something from a ticket description but…
> For me a particularly frustrating aspect is the way the UI moves around a lot. I’m quite anxious to click anything until all the loading spinners have stopped in case I click the wrong thing. Then I could be taken to a page or feature I’ve never seen before. This is a common antipattern that doesn't get talked about enough. It's very common in the era of interactive ads, websites with 3rd party web UIs layered on t…
I feel like hating on Jira is the pastime that is now passed down from each generation of programmers to the next. I'm going to stick up for Jira. I certainly don't "love" Jira, though I do think they've made significant improvements with "new Jira" (I think they call them team-managed projects now). The problem I have with the incessant Jira bitching is that I rarely feel that bitchers have a true understanding for…
Trello was a much better solution to the problem, that's why Atlassian made sure to buy it and is now hard at work ruining it.
OK, so what don't I like about Jira? 1. It's extremely slow. 2. It's difficult to predict the effect of making any kind of change. 3. The permissions system is so convoluted, I can be the admin of a board, and yet not have permission to see a ticket on it. 4. It relegates the conversation to a second-class UI element, when this is the most important part of any project management system. 5. Trying to operate on a bun…
9. The text editor is still busted and I just don't understand why. It's one of the most important parts of the UX, please please fix it. Writing any kind of nicely formatted long form posts is a lost cause.
I feel like hating on Jira is the pastime that is now passed down from each generation of programmers to the next. I'm going to stick up for Jira. I certainly don't "love" Jira, though I do think they've made significant improvements with "new Jira" (I think they call them team-managed projects now). The problem I have with the incessant Jira bitching is that I rarely feel that bitchers have a true understanding for…
I suppose its a necessary evil for an organization of a certain scale, but for whatever reason, I've chosen to work in teams that are small enough that we can dispense with JIRA all together.
Earlier quoted context omitted.
Yeah I've been defended Jira here in the past, too. My opinion is that Jira reflects the organisation that manages it. It's basically a whole lot of customizable UI and permissions hanging off a user-defined state machine. You can set it up so that individual teams can fully administer their own projects, or you can go all the way in the other direction and have centralized, locked-down management where you beg some…
It's not a neutral tool. Jira makes micromanagement easy and trusting people hard; you can use it for good, but you're working against the grain of it the whole time. Everything is default deny (issues can only go through approved transitions, by default regular users can't change the available transitions), the default issue forms have way too many mandatory fields, and a bunch of reports that only micromanagers wan…
I only fill points and name for my issues. My company never customized anything.