131–140 of 287 posts
I really don’t understand the disdain for jira, it is not great but mostly fine. Basically every other tool I have used has been worse. Heard good things about Linear but have a hard time believing that the effort to switch from jira to linear would be worth it for an org.
I always wonder how much of this sort of thing is disdain for the specific tool vs. disdain for what working in a mid-to-large org. is like and the overhead it usually brings with it.
I've wondered the same thing about Microsoft Teams. Is Teams as horrible as people say, or do they just hate it because it's what they happen to use for video meetings at work? Conversely, I don't hear much hate for zoom.
But they pushed out a new version recently. Now you've got Teams Classic and Teams NEW (work or school)... at least on the Mac.
It's sooo much better. Way more stable. Search is a delight (relatively speaking). We get far fewer complaints now.
Worth mentioning: We only use the "Chat" aspect, we don't use the "Teams" aspect. If we want to discuss a project, we just spin up a new chat with relevant parties and rename the channel to the project. Works great. We could never get "buy in" on the Teams aspect, nor threaded discussions. The main reasoning was having to monitor two tabs in the product. Everyone just wanted to stay on the Chat tab, so we made it work.
(No really, Trello is just Jira with cuter, slower menus)
Jira tries to solve everyone’s problem. It tries to incorporate everyone’s idea of how and what’s needed to be tracked. I can just say from my own experience that the one that created the workflow and what fields that they absolutely must have to do some sort of follow up, have never worked as a developer or anything near a software project, and yet enforces all this garbage for their illusion of control. And yet the…
I share the sentiment and frustration of having to fill useless boxes. However, as a manager, things go south very quick if you're not tracking what's being changed and by whom. You won't know what's included in your release, nor if it was tested properly. You won't know who to reach for fixes after testing or even what to tell clients when they ask if a feature/fix was shipped. I hate overly complicated processes, b…
On top of that, I can create a quick form in Confluence (with some intelligence/dependencies) and enabling/disabling/showing/hiding other options, sections, questions, etc.
No complains from either products here. Are they perfect? No. What is?
Earlier quoted context omitted.
When I clicked on the site the very first opinion called Jira shit because they had 20 different boards for the same thing, 2000 tickets in the backlog and 20 different mandatory fields for each ticket. Which is absolutely not the fault of Jira. Jira does not make you create 20 boards and per default a Title is all you need to create a Ticket. By the complaints own wording they had 2000 tickets because management ref…
This hits the heart of it for me. I've used Jira (last job) and Linear (now). I don't really see any compelling reason that Linear is "better" than Jira. Jira was always pretty easy to use and navigate for me, and we had team-focused views for ourselves. Even on this site, several opinions I looked at are about the idea of process or the implementation of a process—not really about Jira. And several of the ones about…
Earlier quoted context omitted.
I've wondered the same thing about Microsoft Teams. Is Teams as horrible as people say, or do they just hate it because it's what they happen to use for video meetings at work? Conversely, I don't hear much hate for zoom.
Teams is the only reason Chrome (well, Chromium) is installed on my work laptop: it detects Firefox and refuses to function. So does Facetime, incidentally, which I found out more recently for a family thing, and that's why Chromium is also installed on my personal laptop currently. I assume they're both doing something unfriendly that Firefox disallows on privacy or security grounds.
Allowing third-party cookies solved my problem (but create others, of course).
I always wonder how much of this sort of thing is disdain for the specific tool vs. disdain for what working in a mid-to-large org. is like and the overhead it usually brings with it.
I work in a mid-to-large org. The more agile part use tools like jira and slack. The older part (established in the 1920s) use Remedy and Teams. Jira is brilliant. It is team-led. Different teams have different approaches, some love all the features like components, versions, issue types, assignee, kanban boards, scrumms, reports etc etc. Others like my team use it with subject/description/comments. You make the tool…
That doesn't sound real. There's supposed to be some central department(s) that collect ideas from the process framework of the season or requested by customers (especially those items for levels that are not requested), add their own ideas and create a superset of that as configuration with everything set to mandatory. The result is infliced upon everyone, except of course the department that was responsible for the definition.
I always wonder how much of this sort of thing is disdain for the specific tool vs. disdain for what working in a mid-to-large org. is like and the overhead it usually brings with it.
I've wondered the same thing about Microsoft Teams. Is Teams as horrible as people say, or do they just hate it because it's what they happen to use for video meetings at work? Conversely, I don't hear much hate for zoom.
So, let's sum up my personal gripes (on a Mac):
1. Teams keeps locking up the dGPU for whatever reason randomly after calls, draining the battery and grilling my legs until I figure out that Teams has gone nuts again.
2. Since the macOS Sonoma update and the switch to the "new" Teams client, every time a call comes in, the ringtone glitches out (and I'm not alone in that)
3. There are three different ways of chatting with other people: Meeting chats and direct/group messages (these are summed up under the "chat" tab) and "teams" with "channels". The latter don't produce instant notifications when someone writes there, I guess because Microsoft doesn't want to deal with "I get an instant notification every time someone posts a kitten photo in the off-topic channel" complaints.
4. There is only one uploaded-files repository which means if you have a "screenshot.jpg" sent to someone, and you try to send a different file with the same name in a different chat, it will say "you already uploaded screenshot.jpg, do you want to replace this?". This is fucking bad UX, likely caused by Teams using OneDrive under the hood to share files.
5. The search is slooooow as molasses and damn useless. You have zero chance of ever finding something again, the larger the org the worse the pain.
6. No window/functionality remembers your context when you switch away. Say you click on a notification from a chat because a colleague needs an urgent answer, while you're scrolling in a team thread... you go back, and your scroll position is lost.