Live data from Hacker News

Linear – A fast issue tracker

linear.app

221–230 of 230 posts

Re: Linear – A fast issue tracker

#221

Earlier quoted context omitted.

Depending on your company culture, this may be difficult to do, but I've seen good luck with moving toward a model where the product team doesn't push things into developers' to-do lists. The product folks supply a strictly prioritized wish list, and developers pull from it. Always one thing at a time, always the very first thing on the list. It's the only way I've seen to get the product people to shift their thinki…

How do you deal with the possible disconnect between product and engineering in terms of feasibility? If #1 on the list is something that will about absorb all of engineering for years, but #2-5 can be developed in weeks each?

Sounds like #1 needs breaking down into many many less tickets!

Re: Linear – A fast issue tracker

#222

Earlier quoted context omitted.

I was a JIRA admin for a number of years for an organization that had a heavy QA workflow. It was all about making sure that every issue had an "owner," at any given time, a strict approval and verification process was followed, and that as much up-front data as possible was collected during the initial report. In my experience, unless the people entering the issues are paid, professional engineers, we'll never get t…

In my experience, it isn't Jira that people hate, it is the horrible rules and bureaucracy-ridden workflows that Jira allows an admin to implement. My team switched back to Jira after trying several other tools and we're pretty happy.

I also don't like JIRA itself, it feels bloated from the get-go.

Re: Linear – A fast issue tracker

#224
post #3

We've been using Linear for a couple months. It's kind of like Superhuman in that the primary benefit is hotkeys. Otherwise it is an issue tracker. I think the reason we see a steady stream of new issue trackers is that teams are trying to fix with software what are people problems. New issue trackers feel faster for the same reason switching browsers tends to feel faster—you're getting rid of all of the crap you pil…

> Don't migrate your backlog, start with only a couple engineers in a new issue tracker... I experienced this in the wiki/documentation space some years ago when my org migrated from the trac wiki to Confluence. It seemed like such a boost initially, but it wasn't a boost at all, it was just the fact that for the first ~12 months after migrating, you could trust that everything you found in the wiki was freshly writt…

https://www.getguru.com/ has a so verification where each page, called cards, has an owner or group of owners and a set expiration period (1 week, 3 months, 1 year etc.). Past the expiration the page gets marked as untrusted (it's on top of each card) and require to be reviewed by the owner(s). Any user can also mark a card as untrusted, prompting a review. Every expired card owned by owner get displayed to their owners in a dedicated UI (page) and can be quickly reviewed. The editor in Guru is a bit clunky at time (worst than Confluence... if that's possible) and not really suitable for something like specs, but I have yet to find anything that actually tries to prevent wiki rot.

We also evaluated Confluence with this https://marketplace.atlassian.com/apps/123/better-content-ar... but if the concept is not a first class citizen in the wiki, it does not work as well.

I tried to convince the people at Clubhouse (with their Write app in beta) and Notion, but I don't think they get it.

Re: Linear – A fast issue tracker

#225
post #192

Atlassian seems to be one of the slowest software companies. They haven't done much to improve their products in all these years. Everything they have is ready to be overtaken by a disruptive product.

Assuming you're correct, I wonder what caused A to slowly change and become slow like that?

From previously having been a bit innovative?

E.g. the many seconds long load times sounds very unexpected ... How did A change so it now accepts things like that? (Or was it always so -- but we were using Jira 5-6 years ago, don't remember having thought of it as slow)

Re: Linear – A fast issue tracker

#226
post #55

Jira is a hot circle of garbage. I am going to check out Linear for my team because I can’t stand how slowly Jira pages load and how long it takes Atlassian to address documented bugs.

Anyone who makes general complaints about Jira like this a) works in a place where Jira has not been correctly configured or b) works in a place with a terrible internet connection c) works in a place where both a) & b) are true or d) doesn't have any idea what they are talking about. P.S. what exactly is "a hot circle of garbage" other than a mixed metaphor?

We use Jira cloud, so if it is misconfigured, blame them. My internet isn’t great, but I will anecdotally note that Atlassian sites are the only ones that ruin a videocon connection. As for your general criticism comment, glass houses.

Last, hot circle of garbage: https://m.youtube.com/watch?v=S70lQwc0FDs

To get specific:

- they’ve had a ticket to hide completed epics from the roadmap open for over a year.

- their user management is a unmitigated disaster. God help you if you use bitbucket or Trello (although Trello users are getting integrated in after 4 years!).

- it took me literally 2 months of help desk tickets to figure out how to get an invoice. The former billing poc was fired, and even though I was the site admin, I had to recreate his account in our SSO, log in as him, and then assign the role to me.

- have you tried to set up even a slightly customized Jira Service Desk?

- want to expire “done” issues faster than 14 days? Pound sand.

- I could keep going, but what’s the point? Atlassian is a bunch of decent products drowning in scope creep, terrible cross-product integration, and a painfully slow development cycle that is focused way more on cosmetic features that fixes their trainwreck of a dumpster fire.

Now that’s a mixed metaphor for you.

Re: Linear – A fast issue tracker

#227

Earlier quoted context omitted.

yes. engineers almost always make poor product decisions if the customer is not also an engineering team, in my (vast) experience. this is because engineers aren't product experts. and if the customer is an engineering team, then engineers mostly make mediocre decisions, typically because of poor incentives (gaming story points). in every company i've been at that is larger than a handful of people that all know each…

>engineers almost always make poor product decisions You seem to be misinterpreting my thoughts as being against the idea of a product manager role. That's not what I mean. I'm talking about product as a separate autonomous org with a CPO, versus embedded PMs reporting to EMs alongside the rest of the product development team. I have similar, though less strong, feelings about Design as a separate org as well, for ma…

>> in my (vast) experience

>Lastly, maybe pump the brakes a bit here, boss. This statement doesn't make me trust you more, independent of your ideas. We're on a web forum, not in a board room.

literally made me lol, thanks for that. i mean it in a good way, not a defensive sarcastic way. that particular phrase is funny. can't recall the movie that made it popular but it forces a smile.

i'm not trying to gain your trust. like 95% of posters, i just like the sound of my own voice. i could not care less what you do with the info ... and i shouldn't care. it's opinionated. if you agree with it, you already agreed with it. it's not like i'm trying to convince you that JWT is bad. i have no agenda.

i was just using the adjective to note that this is what i've seen over a long time in this industry. AFAICT most of HN is 25-somethings with hardly a clue so i felt it useful to note that my opinion doesn't come from the 2 jobs i've held since graduating. that's all. i wasn't trying to speak from a position of authority, so as to command respect.

i understand though why you reacted as such, as in retrospect it sure looks like the typical kind of comment, i'll admit that.

as to the rest of your reply, yup i misunderstood your argument.

as to priority churn, that's not a problem of the backlog per se, that's a function of poor management, or the simple state of being of an early startup. whether you have an actual backlog or not, the whiplash priorities are the problem and the backlog merely the embodiment. by removing the backlog, you haven't addressed the problem.

Re: Linear – A fast issue tracker

#228

Earlier quoted context omitted.

yes. engineers almost always make poor product decisions if the customer is not also an engineering team, in my (vast) experience. this is because engineers aren't product experts. and if the customer is an engineering team, then engineers mostly make mediocre decisions, typically because of poor incentives (gaming story points). in every company i've been at that is larger than a handful of people that all know each…

You're not wrong about incentives, but an org where PMs have fully segregated duties from devs is exactly the organizational context that breeds disconnected engineers juicing their burndown chart. I mean what do you think is the predictable outcome from a PM whose main job is googling his competitors and stuffing high fantasy JIRA tickets in the engineering backlog based on his mystic customer divinations. Neither o…

agreed!

however that's not a [dys]function of simply having a product org, that's a problem with poorly qualified, poorly performing employee. or a poorly describe job function. usually with the boss/management similarly poorly equipped since they don't see past the metrics they themselves (usually) have established for "success".

i think like the GP, you are conflating poor execution of the concept/model with the deficiencies of the model itself. one does perhaps encourage the other, however it doesn't need to be that way and isn't inherent.

i mean, in 3 words, "haters gonna hate". meaning that people that are poor at execution are going to be poor at it no matter the model in which they are embedded. but when you do have a good product team, the product org (as a model) gives them the ability to maximize a less than ideal engineering team. of course, still there's many a slip twixt cup and lip.

Re: Linear – A fast issue tracker

#229
post #55

Earlier quoted context omitted.

Anyone who makes general complaints about Jira like this a) works in a place where Jira has not been correctly configured or b) works in a place with a terrible internet connection c) works in a place where both a) & b) are true or d) doesn't have any idea what they are talking about. P.S. what exactly is "a hot circle of garbage" other than a mixed metaphor?

We use Jira cloud, so if it is misconfigured, blame them. My internet isn’t great, but I will anecdotally note that Atlassian sites are the only ones that ruin a videocon connection. As for your general criticism comment, glass houses. Last, hot circle of garbage: https://m.youtube.com/watch?v=S70lQwc0FDs To get specific: - they’ve had a ticket to hide completed epics from the roadmap open for over a year. - their us…

There are myriad ways to misconfigure a cloud instance of Jira. You thought I was referring to the configuration of the actual web app I suppose. That's kind of a silly assumption but gives me a lot of insight into what you've said here...

A quote from a funny TV show still doesn't really make it a thing, does it?

I don't know that this is the way to fix what you believe to be an open issue. It probably is: https://community.atlassian.com/t5/Jira-Questions/Hide-Close...

If it's not, there probably is a way to do what you are trying to do that you just don't know about.

I work at a very large organization. The user lookups in Jira are lightning fast & the permissions are granular for a reason.

Can't help you with your billing problems but it kind of sounds like a "you" problem.

I have fully configured a Service Desk instance, yes.

It sounds like maybe you aren't actually using the release feature & or that maybe you don't know how to write JQL queries or maybe I don't know anything about the amazingly advanced way you are trying to use the features. "Hey doc, my arm hurts when I do this?" The doctor says "Then don't do it."

I could keep going too but it would be a waste of my time to try & have a reasonable discussion on something which you have prononuced your verdict: "Atlassian is a bunch of decent products drowning in scope creep, terrible cross-product integration, and a painfully slow development cycle that is focused way more on cosmetic features that fixes their trainwreck of a dumpster fire."

All generalizations are false...

Re: Linear – A fast issue tracker

#230

Earlier quoted context omitted.

We use Jira cloud, so if it is misconfigured, blame them. My internet isn’t great, but I will anecdotally note that Atlassian sites are the only ones that ruin a videocon connection. As for your general criticism comment, glass houses. Last, hot circle of garbage: https://m.youtube.com/watch?v=S70lQwc0FDs To get specific: - they’ve had a ticket to hide completed epics from the roadmap open for over a year. - their us…

There are myriad ways to misconfigure a cloud instance of Jira. You thought I was referring to the configuration of the actual web app I suppose. That's kind of a silly assumption but gives me a lot of insight into what you've said here... A quote from a funny TV show still doesn't really make it a thing, does it? I don't know that this is the way to fix what you believe to be an open issue. It probably is: https://c…

https://jira.atlassian.com/browse/JSWCLOUD-17996
Post reply on HN