Also, a fresh JIRA install with no issues, projects, or anything has a memory footprint of over 0.6GB.
I don't know why people use it, but people do. My guess is that all the effort it requires provides a simulacrum of control and productivity.
Also, a fresh JIRA install with no issues, projects, or anything has a memory footprint of over 0.6GB.
I don't know why people use it, but people do. My guess is that all the effort it requires provides a simulacrum of control and productivity.
I will give you this - _should you chose to_ fully mastering it's screens, issue types, screen schemes, issue type screen schemes will take the better part of few hours to completely map in your head. Jira gives you amazing flexibility to do almost anything you want on the issue type level, but with that flexibility, comes an very complex model.
When I first encountered it, I was exasperated that I had to take those couple hours to draw the hierarchy and map it out in my head - but now that I know It, I'm happy it's there.
I agree there is improvement here. But in my years of experience with JIRA, I do find that most software development teams approach things differently, and so there is no 'one size fits all' for most dev teams.
One team wants saved filters to be front and centre, another RSS feeds. One user creates a hundred issues a day (usually QA), whilst others rarely create issues at all.