171–180 of 238 posts
Ten+ years later I had to use Jira in another company and now it's all like expanding panels, sidebars, constantly navigating to different views. I couldnt get a simple straightforward list of issues, or I could only see things assigned to me as opposed to see the progress of the team in a straightforward table...
Earlier quoted context omitted.
Catering to many different kinds of people explains some of the bad stuff, but it does not explain, why seemingly every single Atlassian product including Jira sucks at parsing Markdown or supporting Markdown well. In the big picture maybe some things suffer from catering to too many audiences, but in the small, it is just lack of good engineering. Basically any markdown parser you can install at no cost and even wit…
>it does not explain, why seemingly every single Atlassian product including Jira sucks at parsing Markdown or supporting Markdown well. Australian here, I can provide some clarity on that. Australians in general are fairly lazy; we like to do the bare minimum necessary to get the job done so we can knock off work and grab a beer at 4pm. Atlassian is an Australian company, and has generally inherited such an approach…
If you could do a bloke a favour and chuck up a pull request while we nip down the pub for a coupla you’d be a bloody legend.
Alright piss off now mate.
If the org has a very strict form-filling culture, your Jira tickets will be full of fields to fill for no reason. If no one is valuing documentation, the documents will be outdated or spread randomly. Personally, with the right culture I do not see the problem with Jira, and with the wrong culture Jira can be slog.
The Problem with Jira is not that it's dumb or too sophisticated. The first problem is that everyone, even in the same team or org, needs something different from it. Sometimes it is even single individuals needing one particular thing one time, and the same day for another workflow or view another thing. It is when Jira caters to the wrong use case for you right now where the a lot of frustration arises. In a simila…
Could JIRA be faster, easier, etc...? Sure. But, I have tried many products to run agile/scrum teams and haven't found anything that gives the flexibility and options that JIRA has.
The Problem with Jira is not that it's dumb or too sophisticated. The first problem is that everyone, even in the same team or org, needs something different from it. Sometimes it is even single individuals needing one particular thing one time, and the same day for another workflow or view another thing. It is when Jira caters to the wrong use case for you right now where the a lot of frustration arises. In a simila…
The biggest issue, in my experience, has always been its performance. Perhaps I have only worked in organisations that have completely misconfigured their Jira instances or the servers are underpowered, but even with the Atlassian Cloud, I am used to waiting 10 seconds to move a ticket from one column to another. Or add a ticket to the backlog, click the backlog, ticket isn't there yet, refresh the backlog, it's ther…
There is a lot of fault on the companies who are implementing bad configurations and multiple setups for different teams definitely adds to the complexity. To have a 'lite/light' stripped down version which is purely functional and not bloated with drag and drop events etc would be a really nice to have.
I love seeing competition for Jira, because it needs to die, but I think you need to do a better job explaining your value prop. Your first bullet list of features doesn't really make it sound all that different. Why would I have a better time using this than Jira, bearing in mind that I'd be giving up custom workflows and probably a lot of integrations? (No shade intended. If you can answer that concisely, put that…
> I love seeing competition for Jira, because it needs to die I think when I die in ~50 years that HN will still be filled with stories ragging on Jira, or whatever it is that eventually replaces it. It's like the pastime that will never end. To be clear, I think it's great to see open source projects like this, and I think increasing competition is a really wonderful thing. I also totally agree that Jira has lots of…
I love seeing competition for Jira, because it needs to die, but I think you need to do a better job explaining your value prop. Your first bullet list of features doesn't really make it sound all that different. Why would I have a better time using this than Jira, bearing in mind that I'd be giving up custom workflows and probably a lot of integrations? (No shade intended. If you can answer that concisely, put that…
The value prop is that you can self-host it at all, which JIRA now discontinued unless you pay ~$50k per year. Within 3 seconds of reading the GitHub page I was sold. It’s already on my todo list for next week.
The Problem with Jira is not that it's dumb or too sophisticated. The first problem is that everyone, even in the same team or org, needs something different from it. Sometimes it is even single individuals needing one particular thing one time, and the same day for another workflow or view another thing. It is when Jira caters to the wrong use case for you right now where the a lot of frustration arises. In a simila…
Its too flexible, if you allow people do what they want they'll have no structure at all, and you end up with disasters like a bunch custom "priority" field which are the exact same as the regular priority field except it just has different variations on "low", "medium", "high".
For my team I use basically none of Jiras features. I have a simple kanban board with 7 steps, and encourage my team to use it as a ships log. No story points or sprints or any of that stuff, the only hard requirement is that in order to close a ticket you have to write a paragraph about what was changed or attach an email to the Jira where you did the same but with a client.
The Problem with Jira is not that it's dumb or too sophisticated. The first problem is that everyone, even in the same team or org, needs something different from it. Sometimes it is even single individuals needing one particular thing one time, and the same day for another workflow or view another thing. It is when Jira caters to the wrong use case for you right now where the a lot of frustration arises. In a simila…
Whenever people tell me they hate JIRA, what they are usually saying is they hate the process their company uses. Could JIRA be faster, easier, etc...? Sure. But, I have tried many products to run agile/scrum teams and haven't found anything that gives the flexibility and options that JIRA has.
- the keyboard hotkeys aren't customisable, and often fire when I'm using alt+numbers to switch tabs, so when I come back to the Jira tab it's on some report page I don't care about
- sometimes the content won't render when switching pages, requiring a full refresh. It's difficult to tell whether it's just being slow to load, or it's gotten itself stuck. Sometimes I sit there for a few seconds like an idiot until I remember to hit refresh
- there's pretty poor support for ticket templates as far as I can tell. My company's method uses a confluence page with a table with the templates, then uses the bulk "create Jira ticket" option. But this edits the wiki page for some reason, which you need to revert. They're probably expecting you to duplicate a whole template page before generating, but the editing part could be an option in the generator wizard. With this method there's no way to go back and amend the auto-generated tickets' titles and descriptions etc. You're stuck with manually editing all of them along with the template. Surely templates are a common enough use case that warrant a dedicated workflow?
The Problem with Jira is not that it's dumb or too sophisticated. The first problem is that everyone, even in the same team or org, needs something different from it. Sometimes it is even single individuals needing one particular thing one time, and the same day for another workflow or view another thing. It is when Jira caters to the wrong use case for you right now where the a lot of frustration arises. In a simila…
Whenever people tell me they hate JIRA, what they are usually saying is they hate the process their company uses. Could JIRA be faster, easier, etc...? Sure. But, I have tried many products to run agile/scrum teams and haven't found anything that gives the flexibility and options that JIRA has.
The "better Jira" that I dream of is simply Jira but faster and with a better UI, I don't have issues with the underlying process