JIRA: Help us help you.
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.
Cheers,
Mike
请先登录再写评论。
I'm sure, Mike meant, that you get notified every day about changes, not
that you need to subscribe 365 times a year.
Tom
Now I just need JetBrains to setup RSS feeds for the forums, and happiness will be all over again :)
Initially, these settings were global. I don't know if the default
skins have the ability to make it per person, but I know it has the
hooks for customization.
Norris Shelton
Sun Certified Java Programmer
Colin Fleming wrote:
>Maybe the current version of Jive is the best thing ever, but this one isn't, unless I'm missing something somewhere. For example, in Your Settings/Profile I see exactly 2 options related to display format: Topics per forum listing and Messages per topic listing. Nothing about threaded, flat, tree or any other modes.
>
>I'd love to be corrected on this, or I'd love JetBrains to upgrade...
>
>Colin
>
>
Since this feedback was gathered a month and half ago, can anyone give us an update on what has happened with the feedback and which suggestions are in pipeline for jira?
Thanks,
Jon
Jon Steelman wrote:
Jon,
We have taken all the feedback on board and are working to improve what
we can in JIRA to make it suit the JB environment more.
The biggest problem (NNTP sync to give better access) should be solved
now. We sponsored Mark Derricutt to write an NNTP plugin which I believe
was completed almost a month ago now.
I don't believe it's been installed in the JB JIRA server, though I may
be wrong?
Cheers,
Mike
Mike Cannon-Brookes wrote:
Yep - it's been running for a month or so now,
jetbrains.intellij.jira.idea is the newsgroup.
Mark
It indeed is installed and Mark did a wonderful job of it as well.
R