I was referred to the forums by one of our rabid JIRA users saying that some rabid IDEA users weren't such big fans. I'm here to change that :)
I suppose I should explain myself - I'm one of the two founders of Atlassian - http://www.atlassian.com - the developers of JIRA.
I've also been an IDEA user since it was a JBuilder plugin, JIRA was completely developed using IDEA and every single one of our developers uses IDEA. So I'm not some big stuffy corporate CEO, I'm most certainly a developer at heart.
We pride ourselves on being an open, reactive company - here's your chance to test us.
I can't promise to fix everything in a week, but we will do what we can to make the transition as painless as possible, whilst hopefully showing you why JIRA has so many advantages over the old tracker system :)
I've read through all the threads, and here is what I think the main "pain points" are in the transition to the new system. Once we've worked out a comprehensive list of these problems, we can work to improve things.
Please correct me if I'm wrong or have missed any major items here:
- JIRA has no text formatting in comments
- "I can't understand how to create an issue in JIRA"
- I can't see what issues were fixed in version X?
- I can't search a custom field
- I can't search for issues where build # is between 500 and 508
- JIRA doesn't assign individual modules/components to individual engineers
- Do we need a "two step" system to handle issues in JIRA and the trackers, keeping development issues separate from spurious reports?
- should we duplicate issues between JIRA and the tracker?
- I can't see RSS feeds without assing my username and password
- Can issues be hidden from the public, while sharing others?
- Should a "select group of the community" have access to JIRA?
- How do I get "new / updated issues" in my RSS aggregator?
Did I miss any current problems?
Please feel free to sing out here. I'll respond to these points individually below.