I never hear anyone shilling for them, so now is my chance. Anyone who’s looking for a great JIRA alternative, I love Shortcut (formerly Clubhouse). It’s the best task management software I’ve used aside from the “no task management software” option. Very snappy, updates in real time, notifications make sense, and no workflow-manipulation shenanigans.
Feeling that even they don’t understand what all their epics, stories and milestones do haunted me all the time. Page load times up to 10 seconds and totally unusable on a big screen (just insanely slow after window size bigger then on avarage laptops).
Convincing my company to switch to Linear was better than any holiday.
The concept confusion is the one annoying thing about it. Too many nouns and no rigorous definitions of them. I’ve never encountered page load times, maybe we just have fewer tickets at my job.
gitlab issues seem fine to me. some of the stuff jira does for managers isn't there i guess, but if gitlab solves the engineers problem, having to find a separate tool that can create artifacts for a manager seems like a better idea anyway, one tool per audience.
To elaborate, Linear is probably the best business app I have used for software management ever. For engineers it is fast and fluid and simple with outstanding keyboard shortcuts. For managers it is strongly opinionated with an agile methodology that requires no setup and just works. For teams, Linear makes it fun to stay in sync and track progress towards goals.
One of the best features of Linear is that it inspires my team to build better software, not just tick feature boxes.
Linear is awesome. It gets out of your way and let’s you focus on creating tickets really quickly. The integration with GitHub means engineers rarely need to update the board since tickets sync with your pull request. The keyboard shortcuts are amazing and so is the performance. I’d highly recommend it.
Their pricing and feature breakdown across plans is a joke. Milestones, reporting and roadmap are all top tier features? They're base features on a product like this.
Not once have I wanted reporting or roadmap functionalities as an engineer. Those are management functions, and task management software should serve the people performing the tasks (engineers) first and foremost. Milestones, that’s a bit debatable but still doesn’t seem like core functionality when you have labels and epics.
Filters make no sense? You craft the filters, so if that makes no sense it’s because you didn’t craft the right thing.
What flow? It’s a task management software, not a traffic system. I don’t want it manipulating the flow of anything. It provides swimlanes and that’s more than enough for me. I can move any task anywhere at any time which is exactly what I want out of a software — for it to get out of the way.
No way is Shortcut snappy, at least for EU users. They used it for my last gig and I mostly avoided it as much as possible because the constant 1-5 second page transitions drove me crazy.
+1, I used it while it was still called Clubhouse and it was very pleasant. Its performance is the biggest thing I miss after changing jobs and having to go back to Jira.
Based on my experience from 2-3 years ago, I would say to avoid it. It would be a decent pick for a really small team without a lot of product management expectation, which would probably be served just as well by something like trello.
Example: We wanted to create tasks from Intercom conversations and the only way was a custom implementation. Using their api was not a pleasant experience.
Also there were annoying UI bugs that made the product feel unpolished. I ended up using tampermonkey to fix and improve the UI.
We ended up switching to jira and it’s 100% an upgrade, we were happy with the change. People shit on it when it goes down, same as github, but then it’s all fine and dandy the other 99% of the time.
I've been semi-tracking them because they're a local NYC Clojure shop and had wondered how they were handling the social network name overlap. Glad to hear they're still around.
I just use todoist. Very simple, you can create a bit of structure if you want it, or just keep it very simple as a to-do list & color code priority.
The primary downside is that viewing history (closed tasks) is complete shit. They have an API, and that's the only way of getting history out in any sort of convenient format to review. A very strange oversight.
I'm also not sure how well it would scale to large teams.
How? It seems responsive to me. Most actions result in changing the UI a bit but showing data that’s already preloaded. So no delay waiting for a server roundtrip most of the time.
> Update - Restoration work to restore sites is underway and will continue into the weekend. We are taking a controlled and hands-on approach as we gather feedback from customers to ensure the integrity of these site restorations.
I’ve seen failing Kickstarter updates with more information than this.
Anyway the title isn’t wrong per se but it might be more informative to say a subset of tenants using Atlassian’s SaaS products are down.
If you use any of their products on prem … they are not down. And if you’re not one of the affected tenants then your Atlassian products are fine. At work we have Confluence hosted by Atlassian and it’s up.
According to The Register:
> We were also told that the incident affects a relatively small number of Atlassian customers: about 400. That's only 0.18 per cent of the company's 226,000 customers, which isn't much consolation to the several hundred who still can't access their data.
No, consider that they have an entire team dedicated to their WYSIWYG comment text field and it weighs in at over 20mb(!!!) of JavaScript for a text box.
Atlassian absolutely doesn't care about performance, it should've been obvious when they rolled out "new Jira" a couple of years ago and it was just as slow.
Their priority is adding new esoteric settings that their top customers demand, hence why their settings tab is a labyrinth of spaghetti complexity.
I have no expectation of it; They do everything slowly, regardless of how simple the task, and it’s been that way for ages. And they do ridiculous amounts of configuration.
Im fairly sure at this point it’s just mountains of intermixed logic and death by a thousand cuts; I doubt they could significantly improve performance to approach something reasonable even if they wanted to.
If you're on cloud there's really nothing you can do; on server there are/were some performance tricks you could do by analyzing the SQL queries and designing the fields to be as slim as possible.
Depends what type of project you have. If you're on the next-gen, team-managed project, that was written from the ground up so is supposed to be faster.
The main thing with Atlassian is they royally screwed over all their customers by discontinuing their most popular product and forcing everyone to cloud using really, really unsavory tactics. The only product remaining you can use without cloud had its price increased by an order of magnitude. And, they offered a discount to on-prem customers who signed up for it, and after the fact announced a price increase at least equal to the discount they were offering.
They have decided to treat their customers worse than Oracle does, with nothing but threats that you can make the pain stop if you just go with cloud. They’re an absolutely despicable company.
So after enduring all this, there’s a huge amount of schadenfreude that customers are experiencing watching them be down for so long. They absolutely deserve it.
I would have thought so, but I think it's because people have low expectations of Atlassian that it hasn't gained traction.
In ranking companies by "Ugh, your product sucks" many people would put Atlassian pretty high. So if their product sucks, why would their cloud infrastructure be better?
Wait, do people really have a low reputation of Atlassian? The picture o had in mind was that that pay top $$$, are remote friendly, etc. I would have expected their stuff to be much better...
From what I understand, Atlassian is pushing hard to move everyone to their cloud offerings. I think the only way to run on-prem stuff now is to use the Enterprise or Data Center offerings, which are stupid expensive.
Every place I've worked self hosts and my current company still does. While EOL is still aways away for server (2/2024), it's gonna be a dark day when it arrives.
I'm trying a demo of it and it looks like its mainly aimed at small to medium companies. There isn't enough hierarchy.
The top level organization in Linear is a Workspace. As far as I can tell this should be what your entire company falls under. The next and only level of organization under that is a Team. It really needs something in between that.
Teams have their own Issues, Board (singular), Cycles(Sprints), Projects, Ticket workflows. That means a Team must be a very small set of people (<10 people). So for a company with 1000 employees you might have 100 Teams.
Teams are shown in the UI in a flat list in many places. Expanding the list would likely overwhelm your screen.
The Roadmap feature applies to the entire workspace (your company). In medium sized companies you'll have Organizations with many hierarchies below it comprised of dozens of teams. An Org typically has roadmaps of their own that don't necessarily correspond to company level goals. Teams below the Org will also have their own roadmaps that usually fall under the Org's high level roadmap items but again not always.
There also needs to be more company level controls over settings like workflows. A strict company wide workflow for Bugs is common so that all teams have the same expectations around SLAs for fixes.
All that said I think you could make it work with enough filters and naming conventions.
Also holy hell Linear is fast and easy to use. If I was at a startup I would 100% put us on this.
+1: we use them too and they have a reasonably flexible product in terms of labelling and project definitions. The only notable complaint I have is that the search doesn't support negative filters.
Can Atlassian’s RDS backups be used to roll back changes?
We cannot use our RDS backups to roll back changes. These include changes such as fields overwritten using scripts, or deleted issues, projects, or sites.
This is because our data isn’t stored in a single central database. Instead, it is stored across many micro services, which makes rolling back changes a risky process.
I hate this company and their products so much. The only reason I ever use them is because every single middle manager is obsessed with Jira. Jira sucks and Atlassian is a terrible company.
Readit News
Feeling that even they don’t understand what all their epics, stories and milestones do haunted me all the time. Page load times up to 10 seconds and totally unusable on a big screen (just insanely slow after window size bigger then on avarage laptops).
Convincing my company to switch to Linear was better than any holiday.
Linear was my go-to and I signed up today. I used it at getweave.com and loved using it there
One of the best features of Linear is that it inspires my team to build better software, not just tick feature boxes.
Deleted Comment
Their pricing and feature breakdown across plans is a joke. Milestones, reporting and roadmap are all top tier features? They're base features on a product like this.
I had the complete exact opposite experience. I actually do wish we are still on jira.
it's slow. It's filters make no sense. It's entire flow make no sense.
What flow? It’s a task management software, not a traffic system. I don’t want it manipulating the flow of anything. It provides swimlanes and that’s more than enough for me. I can move any task anywhere at any time which is exactly what I want out of a software — for it to get out of the way.
I've been semi-tracking them because they're a local NYC Clojure shop and had wondered how they were handling the social network name overlap. Glad to hear they're still around.
The primary downside is that viewing history (closed tasks) is complete shit. They have an API, and that's the only way of getting history out in any sort of convenient format to review. A very strange oversight.
I'm also not sure how well it would scale to large teams.
I’ve seen failing Kickstarter updates with more information than this.
Anyway the title isn’t wrong per se but it might be more informative to say a subset of tenants using Atlassian’s SaaS products are down.
If you use any of their products on prem … they are not down. And if you’re not one of the affected tenants then your Atlassian products are fine. At work we have Confluence hosted by Atlassian and it’s up.
According to The Register:
> We were also told that the incident affects a relatively small number of Atlassian customers: about 400. That's only 0.18 per cent of the company's 226,000 customers, which isn't much consolation to the several hundred who still can't access their data.
(My employer will switch away from Atlassian products once they don't offer on prem anymore.)
And Jira has been really great. The sprint boards, concept of mapping statuses to in progress etc have all been great.
My one gripe (and it’s not a small one) is performance. It still feels quite sluggish. Is Atlassian ever going to address this?
Atlassian absolutely doesn't care about performance, it should've been obvious when they rolled out "new Jira" a couple of years ago and it was just as slow.
Their priority is adding new esoteric settings that their top customers demand, hence why their settings tab is a labyrinth of spaghetti complexity.
I’ve been using Jira for almost a decade now. Pretty sure it gets slower and slower.
Im fairly sure at this point it’s just mountains of intermixed logic and death by a thousand cuts; I doubt they could significantly improve performance to approach something reasonable even if they wanted to.
oh my sweet summer child
I've used several bug trackers including JIRA. Gitlab has been my best experience.
But the reports only do it by open and closed. We only merge/close when we’re releasing the ticket.
Deleted Comment
Just asking, I’ve never used any of their products
They have decided to treat their customers worse than Oracle does, with nothing but threats that you can make the pain stop if you just go with cloud. They’re an absolutely despicable company.
So after enduring all this, there’s a huge amount of schadenfreude that customers are experiencing watching them be down for so long. They absolutely deserve it.
In ranking companies by "Ugh, your product sucks" many people would put Atlassian pretty high. So if their product sucks, why would their cloud infrastructure be better?
It's fine. Certainly no worse than any other wiki that just accretes content.
(Then again, we're not doing anything overly sophisticated with it, or relying on any of its features for critical workflows.)
i've definitely been using bitbucket and jira for the last four days without noticing anything wrong.
All I was looking for after the slugfest of Jira was fast performance and keyboard shortcuts, and so far linear has been able to deliver.
The top level organization in Linear is a Workspace. As far as I can tell this should be what your entire company falls under. The next and only level of organization under that is a Team. It really needs something in between that.
Teams have their own Issues, Board (singular), Cycles(Sprints), Projects, Ticket workflows. That means a Team must be a very small set of people (<10 people). So for a company with 1000 employees you might have 100 Teams.
Teams are shown in the UI in a flat list in many places. Expanding the list would likely overwhelm your screen.
The Roadmap feature applies to the entire workspace (your company). In medium sized companies you'll have Organizations with many hierarchies below it comprised of dozens of teams. An Org typically has roadmaps of their own that don't necessarily correspond to company level goals. Teams below the Org will also have their own roadmaps that usually fall under the Org's high level roadmap items but again not always.
There also needs to be more company level controls over settings like workflows. A strict company wide workflow for Bugs is common so that all teams have the same expectations around SLAs for fixes.
All that said I think you could make it work with enough filters and naming conventions.
Also holy hell Linear is fast and easy to use. If I was at a startup I would 100% put us on this.
Can Atlassian’s RDS backups be used to roll back changes? We cannot use our RDS backups to roll back changes. These include changes such as fields overwritten using scripts, or deleted issues, projects, or sites. This is because our data isn’t stored in a single central database. Instead, it is stored across many micro services, which makes rolling back changes a risky process.
Also, screw Atlassian for acquiring Trello.