231–240 of 305 posts
Earlier quoted context omitted.
Check out Clubhouse.io I've used many others including Github, GitLab, Phabricator, Redmine, etc., and Clubhouse does a great job IMO.
My org uses Clubhouse, and it's still slow. Probably not as slow as Jira, but it's a running joke where I work.
We recently passed 10k stories and it still feels very snappy. Also the UI/UX feels very polished.
Earlier quoted context omitted.
My org uses Clubhouse, and it's still slow. Probably not as slow as Jira, but it's a running joke where I work.
Interesting! What size org? We recently passed 10k stories and it still feels very snappy. Also the UI/UX feels very polished.
Earlier quoted context omitted.
Hi michaelt, Thank you for the numbers -> I agree these are slow, and I can guarantee you that the Jira team is working on it (though I can't talk about details). These numbers are definitely outside of the goals. I appreciate the call out of "page to complete rendering and the progress bar at the top of the screen to disappear" and "until the issue, comment and buttons have all loaded". In a dream world of course, e…
I hate to pile on a thread where you're already taking a lot of flack, but this point is really important to the future of Atlassian: > In a dream world of course, everything would load in As a contractor, I have more or less walked out of or refused interviews on discovering Atlassian toolset was in use. It's not because I hate your tooling (it is visually nice and very featureful), it's because the culture that del…
All these systems suck. You learn to live with them, for me I do this:
Everything goes in OmniFocus, I have a keyboard shortcut to create a task that takes 15 mins before I finish work for the day at a client, I update whatever ticket system they use (mostly Jira, but also sometimes even worse things like servicenow) and also whatever enterprise crapware my agency uses (usually some sap based bollocks).
The last 15 mins suck. But it's part of the deal. I can't imagine how strongly you feel to turn down contractor rates due to a ticket system.. I mean, come on?
Edit: Also - btw -- if you're on a Mac the app-store 'fat-app' version of Jira is about 10x better than using the web interface, I suggest you give it a try.
Earlier quoted context omitted.
Interesting! What size org? We recently passed 10k stories and it still feels very snappy. Also the UI/UX feels very polished.
We're barely over 1k employees, and most of those don't use Clubhouse. Not sure how to tell exactly how many stories we have in CH.
I'm curious, I'm a Cloud customer and I can tell you that the service is incredibly slow even for a small scale setup (2 Jira Projects and 3 Confluence Workspaces). There's an insane amount of network requests seemingly for mouse tracking. By telling everyone here, that Atlassian Cloud products are insufferably slow, am I violating the ToS? I was actually thinking about doing a write up on the issues I've had but thi…
On a YouTube lecture at CMU the Materialize guys seemed to try very hard to not even land in the same zip code as that discussion to the point it was awkward, and they seem pretty smart.
Are these large organizations really that petty? Ad absurdism, would it be legal if Ford said we couldn’t drag race their car after we bought it?
Earlier quoted context omitted.
who says this is an "issue" its just numbers. If you think its an issue thats your interpretation. For instance I used jira for communicate with my team about 3 projects and it only took me 3 hours. Maybe this person is writing a fiction story where the protagonist is using Jira and they are detailing how they spend their day. Its like a John Steinbeck novel
May I point you to the title of this submission? "Atlassian Cloud ToS section 3.3(I) prohibits discussing performance issues" No sane judge would agree with your interpretation.
Earlier quoted context omitted.
I hate to pile on a thread where you're already taking a lot of flack, but this point is really important to the future of Atlassian: > In a dream world of course, everything would load in As a contractor, I have more or less walked out of or refused interviews on discovering Atlassian toolset was in use. It's not because I hate your tooling (it is visually nice and very featureful), it's because the culture that del…
Hmmm. I mean. I'm a contractor too, and I share your pain, but ... I'm really impressed you walk out of paid work because of the issue tracker your client uses.. It sounds a bit like they dodged a bigger bullet than you did tbh mate. All these systems suck. You learn to live with them, for me I do this: Everything goes in OmniFocus, I have a keyboard shortcut to create a task that takes 15 mins before I finish work f…
Earlier quoted context omitted.
As a first step, 1s would be better than nothing for sure, but you need to be working towards a much tighter goal on a 1-2 year timeframe. New load, you should really be hitting 200ms as your 95th percentile - 300ms or so would be decent still. "Transitions" should hit 100ms 95th, 150ms would be decent. If you did hit 100ms across the board, you'd be rewarded by your customers/users psychologically considering the in…
Thank you for coming back and clarifying. Do you happen to have links to any public testing results of other tools, or guidance to this specificity - would love to use them to build a case internally Most of what we've seen online are nowhere near this level of detail (X-ms for Y-%ile for Z-type of load) (edit: clarified request)
Sorry if that’s pointed, but it’s sort of meant to be incredulous (but hopefully not offensive).
Earlier quoted context omitted.
Not to mention the reputational damage from people asking "why the hell is this in the contract in the first place?" It says they're so afraid of the quality of their product they'd rather litigate their customers than fix their product.
I wonder if these should be called "Streisand clauses", because it seems that the net effect will be for people to increasingly associate Atlassian with badly performing software. Certainly if someone asked me what I know about Atlassian, this would now be one of the first things that come to mind.
I moved my team to clubhouse, even-though it created an element of fragmentation considering all other teams are using JIRA. I'm so happy though with clubhouse, I can actually get my work done without mindlessly waiting for every interaction.
Icing on the cake: I was considering moving the company over to Jira on a self hosted AWS instance, I've read that it can be a little faster. but.. they're discontinuing the self hosted option. Nail in the coffin for me.
Good bloody riddance.