111–120 of 530 posts
RT @HackerNewsOnion: California has ruled it illegal to conceal a company’s JIRA subscription for the purpose of attracting engineers. https://twitter.com/HackerNewsOnion/status/98160924222131814...
1. When editing a comment, the textarea is tiny and placed in a pop-up, instead of in the page. Can't resize that to see the comment better.
2. After disabling shortcut overrides, the shortcuts are simply disabled, along with the default browser behaviour for them.
3. Refreshing a page resets scroll-status. Seriously, webdevs, stop hijacking normal browser scroll behaviour. You always make it worse, never better.
4. If your login session times out when you're writing a comment, you can't publish it, but the error message isn't clear about the reason why. There was some button in the error message that caused you to lose the entire contents of the comment you were writing. Happened to me several times after writing comments 8+ paragraphs long. It's infuriating.
Can someone - anyone - recommend a better product (non-cloud)?
Phabricator.
You also have to pay to even comment on issues. I think that's a pretty great way of getting companies to pay for support but it's also annoying if you want to work with other freeloaders on issues.
Also it's written in PHP which means you aren't ever going to want to read or modify the code. No different to GitHub, or probably even GitLab but I can definitely imagine modifying Gogs/Gitea.
Earlier quoted context omitted.
Native support for Markdown in comments would be a good win. In the Atlassian ecosystem, the markup languages are constrained by the following equation: JIRA Markup != Confluence Markup != Bitbucket Markup
Also even just within JIRA it can be inconsistent - I realised that to make monospaced text you need to use: - backticks when creating a Jira ticket, e.g. `hello` - double curly-braces when editing a Jira ticket, e.g. {{hello}} ... or vice versa. I cannot honestly remember which way round it is. Of the complaints I have about Jira this is probably the least annoying - but it really shows how irritating the product is…
I remember this caused me some data corruption when editing a comment created with the old version of the editor using the new editor. It was a mess.
Earlier quoted context omitted.
Phabricator.
Phabricator is pretty good except it has pretty much zero CI integration. Kind of annoying. You also have to pay to even comment on issues. I think that's a pretty great way of getting companies to pay for support but it's also annoying if you want to work with other freeloaders on issues. Also it's written in PHP which means you aren't ever going to want to read or modify the code. No different to GitHub, or probabl…
OP mentioned "non-cloud", so I assumed they wanted it self-hosted. You don't have to pay anyone for commenting in Phabricator when you're self-hosting it.
I have used a whole bunch of ticket/project managing tools in a number of different orgs. By far the most useful is JIRA.
taiga.io comes close, but lacks the admin interface and multi project overview that jira has.
Trello is ok, but terrible for large teams, or large projects. Subtasking is a pain and there is no real concept of a sprint. its ok for replacing notes on a board, but terrible for recording state.
Some of these criticisms are valid, but compared the competition[1], I'd choose JIRA 7 times out of 10.
[1] dont get me started on the "clever" people that decided to make their own in house solution, kneecapping the entire planning ability of a 70k person org.
Every bullet point says "Missing...", but I feel like the main issue about Jira is that it has waaay to many features, and that it's super slow! The only bullet point I do agree with, is that Jira is missing an easy (or IMHO a minimalist / simple) interface. The tool is a mess, and the people using it are probably also using it in the wrong way, making the whole situation way worse. Don't get me wrong, I like Jira to…
> Every bullet point says "Missing...", but I feel like the main issue about Jira is that it has waaay to many It says "missing" but it mostly talks about those existing features lacking any polish. > and that it's super slow! It is and it really sucks or to quote Firefox "A web page is slowing down your browser, what do you want to do, wait or stop it".
Atlassian seems to make a lot of money, so I guess they're optimising for something that matters to someone, but from my point of view I have a simple process for evaluating tools:
1) Can I use it at all? 2) How many of the features I want does it have?
I'm pretty sure Jira would score great on the second question, but since it hard fails the first, I'll never know. And it's been slow for so many years now, I assume they have no interest or ability to fix it. And their slow drift towards cloud installs over letting people self host isn't helping them either since, embarrassingly, their cloud instances seem to be even slower.
(Incidentally, there's a lot of competition in that space, but I've been pretty happy with Clubhouse. I wouldn't mind a few more features, but it's good enough. More importantly, the UI is clean and snappy, and that hides a multitude of sins.)
Earlier quoted context omitted.
Jira Cloud has a new editor that is Markdownesque. Type as if you're using Markdown, and it will do the formatting you'd expect.
From your description, it sounds like this would have Slack's problem (which resulted in one of the most upvoted HN threads of all time, https://news.ycombinator.com/item?id=21589647 ). I've tried Googling around a bit to find an example of Jira Cloud's Markdown environment, but couldn't find one. (I am certainly biased, though, by my strong loathing of Jira.)