4 ms·

I'd need to be paid a lot more than that to use JIRA.

ghshephard 16y ago
So, the one painful part of Jira, that Atlassian really needs to do something about, (And I say this as a Die-Hard Jira fan with four years of absolute devotion to the product) is the simplification of their field-issuetype-screen-schemes, as well as the myriad other schemes. It took me over a year, and at least five or six sessions of sketching it out onto paper, before I was able to mentally map Custom-Fields, Screens, Issue Types, Priorities, Resolutions, Statuses,workflows and their various schemes in my head. One part that makes it problematic, is Jira is not _consistent_ in how you map schemes to collections of atomic elements like Statuses or Resolutions (Their are no IssueType-Status-Schems, or IssueType-Resolution-Schemes, but there are Field Configuration Schemes, and IssueTypeScreenSchemes) But, with that one exception, the software is a delight. Fast, even on a tiny platform. Takes 3 minutes to install (The hardest two steps are setting your JAVA_HOME variable and mapping your Server Directory in a config file) - works on WIndows, Linux, Mac with zero issue. Very extensible, great plugin community. The new 4.x JQL makes sophisticated queries against your issue database a dream. And it scales well - Our three Gigabyte Memory, 12 Gigabyte Disk VMware Machine has added 18,962 issues this year, and continues to feel light (Now totalling 68,495 issues). I can type a query like "+VPN +Bandwidth" - and get an answer back in about 2 seconds (Thanks Lucene!) - this with a full text search of all the comments, descriptions, and summaries. I love the product so much that I even enjoy the people who have issues with it - Nothing better than to have someone point out a problem, and then come back with a 15 second solution that also provides the foundation for solving a whole host of other problems. It has my recommendations with only minor reservations regarding the complexity (and inconsistency) of their schemes. Remedy, on the other hand, gets no recommendations whatsoever for their out-of-the-box implementation. I'd love to find someone who has anything to say something good about that product.
- kelnos 16y ago
  > Fast, even on a tiny platform. Really? We have it running on a 2x4 core Opteron 2.2GHz system with 4GB of RAM, supporting barely 60 people, and page load times are slow as hell. And it was even installed and set up by a consultant. > Takes 3 minutes to install Sure, if you don't mind that the default install uses (and warns you about!) a non-production-worthy database to store your data.
- kemiller 16y ago
  The schemes of schemes thing is very maddening, since I never know which level I'm supposed to work on. The usability is awful. Actions listed alphabetically in the side bar? Including "edit"? Really? We get frequent, intermittent crashes. I think if we really needed the flexibility, I'd appreciate it more. We don't really, so it just seems like a bloated, confusing mess.

So, the one painful part of Jira, that Atlassian really needs to do something about, (And I say this as a Die-Hard Jira fan with four years of absolute devotion to the product) is the simplification of their field-issuetype-screen-schemes, as well as the myriad other schemes. It took me over a year, and at least five or six sessions of sketching it out onto paper, before I was able to mentally map Custom-Fields, Screens, Issue Types, Priorities, Resolutions, Statuses,workflows and their various schemes in my head. One part that makes it problematic, is Jira is not _consistent_ in how you map schemes to collections of atomic elements like Statuses or Resolutions (Their are no IssueType-Status-Schems, or IssueType-Resolution-Schemes, but there are Field Configuration Schemes, and IssueTypeScreenSchemes) But, with that one exception, the software is a delight. Fast, even on a tiny platform. Takes 3 minutes to install (The hardest two steps are setting your JAVA_HOME variable and mapping your Server Directory in a config file) - works on WIndows, Linux, Mac with zero issue. Very extensible, great plugin community. The new 4.x JQL makes sophisticated queries against your issue database a dream. And it scales well - Our three Gigabyte Memory, 12 Gigabyte Disk VMware Machine has added 18,962 issues this year, and continues to feel light (Now totalling 68,495 issues). I can type a query like "+VPN +Bandwidth" - and get an answer back in about 2 seconds (Thanks Lucene!) - this with a full text search of all the comments, descriptions, and summaries. I love the product so much that I even enjoy the people who have issues with it - Nothing better than to have someone point out a problem, and then come back with a 15 second solution that also provides the foundation for solving a whole host of other problems. It has my recommendations with only minor reservations regarding the complexity (and inconsistency) of their schemes. Remedy, on the other hand, gets no recommendations whatsoever for their out-of-the-box implementation. I'd love to find someone who has anything to say something good about that product.

kelnos 16y ago
> Fast, even on a tiny platform. Really? We have it running on a 2x4 core Opteron 2.2GHz system with 4GB of RAM, supporting barely 60 people, and page load times are slow as hell. And it was even installed and set up by a consultant. > Takes 3 minutes to install Sure, if you don't mind that the default install uses (and warns you about!) a non-production-worthy database to store your data.
kemiller 16y ago
The schemes of schemes thing is very maddening, since I never know which level I'm supposed to work on. The usability is awful. Actions listed alphabetically in the side bar? Including "edit"? Really? We get frequent, intermittent crashes. I think if we really needed the flexibility, I'd appreciate it more. We don't really, so it just seems like a bloated, confusing mess.