6 ms·
I hope those now remote employees have access to some good issue tracking, repo hosting, and collaboration/documentation tools. Else they'll be forced to use s
by coldtea 6y ago
I hope those now remote employees have access to some good issue tracking, repo hosting, and collaboration/documentation tools.
Else they'll be forced to use something like Jira, Confluence, Bit Bucket, and such, which suck...
- entropea 6y agoI am directly responsible for Jira and Confluence admin/infrastructure on an enterprise level and once you know how at least Jira works, its a fairly powerful tool for PM's. I haven't run into many issues except during a migration where we knew we were going to run into issues. Atlassian's documentation isn't that good however.
- JoshTriplett 6y ago> its a fairly powerful tool for PM's That's the fundamental problem. Jira is sold to PMs and managers, not to developers, and it shows. Jira isn't an issue tracking tool, it's a work-tracking and developer-tracking tool masquerading as an issue tracker. The people who spend the most time with it aren't the customer.
- marmaduke 6y agoI use Jira to track issues. It’s not as pretty and dumbed down as Github or as dandy as YouTrack but does the job fine over the last 8 years we used it.
- entropea 6y agoYou can set it up to be an issue tracker or you can set it up to be work & developer tracking. It's really dependent on how your PM sets your projects up.
- lemmsjid 6y agoInteresting how perspectives differ. Having used Jira for many years, I think it's straightforward for engineering work, but particularly hard for PMs and managers. Why? On the engineering side, it's pretty straightforward to integrate into a lifecycle. But for PMs and management it's a nightmare because they still haven't gotten their birds-eye-view roadmapping / bulk editing act together. The usual issue I have with Jira is that the engineering team gets it integrated into their workflows, things work ok, but it's a continual challenge getting global rollup views to the business at large. We keep ending up with Excel, Airtable, or what-have-you high level views that then point to particular Jira issues for details (yes, we've used Portfolio). I think this actually might be a fundamental issue that is masquerading as design issues on Jira's side, because when you're doing roadmapping views you want to continually refactor them to reflect better metaphors and realities, whereas when you're doing issue tracking you want issues to stick around and be solid entities linked intimately into the history of the software application. So tools like Portfolio have to juggle both ends.
- Izkata 6y agoThis is pretty much my experience as well - Jira is used almost entirely by developers (and we set up the statuses/transitions/etc in the ways we find useful), while product organizes their thoughts in Excel/Google Sheets and will create/watch/comment on Jira cases but mostly not otherwise use it.
- deleted 6y ago[deleted]
- fennecfoxen 6y ago> Jira is sold to PMs and managers, not to developers, and it shows When you're working with Python, Jira will render __init__.py as an italicized version of _init_.py even when you put it in monospace with the {{braces}}. If you're talking more abstractly about algorithms, O(n) turns into the letter O followed by the thumbs down emoji. It's a good thing no one uses Jira for software projects because that'd be really awkward!!!
- stjohnswarts 6y agoCan someone explain what is hard about Jira to me? I push bugs and pull bugs and spend maybe 20 minutes a day in it. What is hard about it? Am I just at a place that uses it sanely? Once a week we spend maybe 1 or 2 hours in it review/updating the Agile sprint buckets with the group.
- user5994461 6y agoYou must at a place that is sane enough. A non sane place would have 20 obscure mandatory fields per ticket, require the ticket to go through 10 different states that makes no sense, and last but not least, every click would take a full minute to load the page.
- JoshTriplett 6y agoOne of the other problems with Jira is that it's incredibly easy to create complex Byzantine workflows, dozens of required fields to file or update an issue, and reports based on those files. That makes it easy for a bad PM or manager to take their own hard questions to answer and turn them into endless bureaucracy for developers.
- Hamuko 6y ago>once you know how at least Jira works, its a fairly powerful tool for PM's. I'm not a PM and I don't really want to get to know the ins and outs of an issue tracker.
- entropea 6y agoI'm not entirely sure why you'd comment this in the first place? If you're a developer you simply need to login and look at your project, not really know much else except how to click issue buttons. I'm talking from an administrator standpoint. Developers also aren't the center of the universe no matter how much we think we are.
- Hamuko 6y agoMost of the tickets in our JIRA are made for the developers, not for the PMs or the customer support. Also, looking at my project is a pain since my tickets are outside the sprint and I either need to go into the backlog and scroll a bunch, or use a custom search.
- stjohnswarts 6y agoUnless you're a micromanager that's the way it should be. She see issues opening and closing and estimates on it. If those estimates blow up/linger on and on then the PM is needed to pull together resources and get it finished off. I don't see how it's a big deal. I've used it both as group lead and as a programmer and didn't have many issues with it either way. Sure it's a bit laggy but it's not that bad. It would be a lot nicer if they'd made a native client that has better queuing/caching of tasks to let you do many things at once.
- triceratops 6y agoJira is achingly slow. Confluence has the worst search in the world.
- pm90 6y agoBoth JIRA and confluence are slow and the UI's are horrible and incredibly unresponsive by modern standards. It shouldn't take several seconds to load my JIRA board. Fuzzy searching for issues should just work. Collaborating over JIRA on a video conference is PAINFUL AF. A lot of time is spent just waiting for the UI to respond. It is completely unacceptable.
- skrap 6y agoCurious if you use self-hosted or cloud jira? My main problem with (cloud) jira is that it takes about 30 seconds from navigating to the site until I can start typing my issue comment or description or whatever. And that's without using search... It's just _so_ slow.
- secondcoming 6y agolmao, i don't mind jira, but bitbucket sucks all the balls
- dhbradshaw 6y agoApparently I'm in a minority but I love Jira for remote work.
- deleted 6y ago[deleted]
- dirtnugget 6y agoI also don't get the hate. All other tools I had to use were garbage in comparison
- Solstinox 6y agoYou know what’s worse than having to work with JIRA/Confluence/Bit Bucket, and such? Working with people who keep changing systems every 6-12 months. A crappy system used fully is better than system surfing to find the Holy Grail™.
- rad_gruchalski 6y agoSo, like jira every couple of months? Festures removed, ui changed...
- LifeLiverTransp 6y agoBraile is the new flat UI - you will love it once, you give this UX a try
- dijit 6y agoMan, I’d agree with you if my experiences with these tools wasn’t _so bad_. The current implementation of jira and confluence I’m using is worse than having _no_ ticket tracking and documentation system. Because if it didn’t exist there would be the impetus to implement something. But we just kinda barely limp by with what we have. It’s so barely functional that people actively avoid using it. I’m fully aware that the company is to blame and not necessarily atlassian though, as we have a number of plugins and random custom fields. One of the most dangerous things about jira is that it tries to be everything to everyone and people get carried away in the customisation believing they need it. It slows everything to a crawl and leaves you inundated with mandatory fields and a nightmare of matching stories with sprints and estimations in order to bring a bloody task in. Life was better with rt and mediawiki.
- JoshuaDavid 6y agoI think you're underestimating how bad the "something" people can come up with is. Think "weekly status reports to describe how you're doing on fixing a problem that was described through email, or an in-person meeting with someone, or a phone call, and never entered into a ticketing system at all". Also the mandatory fields are definitely a per-organization thing. At my org we have I think 3 mandatory fields, which are the project the ticket goes under, the title, and the description. In many cases, "migrating" from JIRA to JIRA but 90% of the features are disabled would probably be an improvement.
- sg47 6y agoThank God they discontinued Hipchat.
- drewg123 6y agoOdd, that's the one atlassian product I like. I remember it as being better than slack..
- Orou 6y agoI actually liked Hipchat. It did what it was supposed to do - provide instant chat with colleagues - without the overhead and frills of Slack. It was simple and reliable. I'm not sure why it was so disliked.
- hinkley 6y ago> It was simple and reliable.
- stjohnswarts 6y agoWhat is hard about slack? We use channels for the "group" stuff and IM for quick and dirty chats, otherwise just pick up the phone and call. I personally just prefer using email, but the kids like their slack/discord/whatever
- hinkley 6y agoI had a friend complain it was eating their battery, and my phone battery started acting weird around the time I installed it. Seems better now, did they ever confess to a problem?
- babaganoosh89 6y agoThe memes were also better
- laurent92 6y ago
- hinkley 6y agoI have a tiny sliver of hope that they will see how it behaves on a slow network and fix some stuff. One day I need to have a beer with these people who say Jira is fast. I've seen everything from "unremarkable" to "If we don't reboot the servers on Monday then nobody can work after 10 am on Friday". But never, ever, fast.
- stjohnswarts 6y agoAll those things work fine as long as you don't penny pinch on servers. If you do ignore scaling, then yeah it's gonna be slow and horrible.
- ergocoder 6y agoI raise you the issue tracker Google Chrome uses. it's bad in every way.
- wubbalerfa 6y agoFor anyone who is already used to Jira and considering switching, think again. Monday seems to be popular as the "much faster, responsive" competitor if the marketing is to believed. I've used it for 6 months - it's garbage. At least, absolutely ZERO times better than Jira as an overall productivity tool. I can't tell you how many times issues have never loaded (see: blank screen), painstakingly prioritised lists of HUNDREDS of issues that have had their ordering completely scrambled, to name two off the top of my head. If you hate Jira, think about whether it's the thing you hate that you're used to. Because you're absolutely going to be trading for a NEW thing that you hate, and have to learn to use from scratch.
- deleted 6y ago[deleted]