101–110 of 230 posts
I tried a ton of other trackers, my second favorite being Notion. Reason we left Notion was lack of an API.
Even though it lacks some basic features, a graphQL API that means I'll never be missing an endpoint and webhooks keep me happy.
For example, I have a step in CI to move issues from staged to deployed. Also then moves associated hubspot to tickets to a queue for CS to inform the customer.
This may be a minority opinion, but I'm disappointed that so many core workflow apps like ticketing still living in the browser. Any serious programmer would scoff at the idea at their main IDE being within a browser, so why is it acceptable for a ticketing system, which is nearly as core to our workflows?
Earlier quoted context omitted.
Not sure what happened to you - but speaking anecdotally, but from someone who logs into Jira Cloud every day, and spends 20-30 minutes interacting with the interfaces over 8-10 hours a day, and has done so for the last 3 years - it's had a handful of outages, nothing that really rose to the level of being memorable though (and less than any internal issue tracker I've worked with) - and the performance is, fine? I m…
Ours JIRA instance took multiple seconds to load modals. Think 5+ seconds. It was miserable. I would have gladly paid more for faster speed but it turned out the APIs were blazing fast and it was the JS that was slow. Not sure how we have had such different experiences. Seems impossible that your JS was executed that much faster than mine. I was using chrome FWIW.
This may be a minority opinion, but I'm disappointed that so many core workflow apps like ticketing still living in the browser. Any serious programmer would scoff at the idea at their main IDE being within a browser, so why is it acceptable for a ticketing system, which is nearly as core to our workflows?
Are you talking about just the browser chrome or the actual implementation? Because maybe it means that I'm not a serious programmer, but I love VS Code.
The filesystem access issues make IDEs a bit different than issue trackers IMO, I don't have a problem with an issue tracker living in a browser, or being browser + Electron options.
This may be a minority opinion, but I'm disappointed that so many core workflow apps like ticketing still living in the browser. Any serious programmer would scoff at the idea at their main IDE being within a browser, so why is it acceptable for a ticketing system, which is nearly as core to our workflows?
This may be a minority opinion, but I'm disappointed that so many core workflow apps like ticketing still living in the browser. Any serious programmer would scoff at the idea at their main IDE being within a browser, so why is it acceptable for a ticketing system, which is nearly as core to our workflows?
I have a rough time understanding why I'd pick this over the issue tracker integrated with my source control. I get that it can sync with GitHub or GitLab (Does it sync the issue text/comments such that GitHub users can comment on the issues? Are the issues on both sides using the same numbering? In this case, is Linear just a GitHub issues client?) but I imagine I am losing out on any given feature that my source co…
You don't want your issue tracker in your source control if your product includes multiple source repositories, and a single bug might span several, or need to move between them. Also, if you have customers who file bugs, they don't care about your code structure. And maybe they shouldn't have read access to your code?
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?
Doing anything in Jira / confluence is really slow. It’s a nightmare to navigate and it seems like every time I click on anything, it takes 2-3 seconds to load.
It’s really hard to explain but I guarantee you that if you tried linear out, you’d “get it”.