On JIRA (New Year's resolution:)

Hello All,

People often ask us what is the exact purpose of having as many as 3 different
JIRA projects for IntelliJ IDEA. For those of you who are interested, here
is the updated explanation: http://www.jetbrains.net/confluence/display/IDEADEV/Workingwithissue+tracker

So far noone has been very happy about our issues tracking. For one, "IDEA
Feedback" project used to be full of unattended issues.

We have done some cleanup work recently. From now on we are really trying
to be more responsive. In particular, we do not want to keep an issue in
the Feedback project for more than 30 days (see the guidelines for details).

This means more issues will be moved to IDEA Backlog or closed as "Won't
fix". It might be not the nicest fate for an issue, but if we know we are
not going to implement something soon (or ever), we would rather tell you
the truth.

One thing I would like to point out specifically: IDEA Backlog is not an
issues graveyard. Issues may and will be pulled back to IDEA Development,
if they collect enough votes. We have already revived some backlogged issues
during our cleanup effort.

And here is a list of issues about which we are not quite sure what to do
(http://jetbrains.net/jira/secure/IssueNavigator.jspa?reset=true&pid=10131&status=10001).
Please vote for them if you like them, or comment if you think the feature
is useless/harmful/misguided.

Best regards,

Vladislav Kaznacheev
Project Manager, IntelliJ IDEA
http://www.jetbrains.com
"Develop with Pleasure!"


6 comments
Comment actions Permalink

This means more issues will be moved to IDEA Backlog or closed as "Won't
fix".


Isn't that the same?

0
Comment actions Permalink

Hello Tom,

>> This means more issues will be moved to IDEA Backlog or closed as
>> "Won't fix".
>>

Isn't that the same?


Sorry, but have you read the message to the end?

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Thank you for this. Let's hope you guys are better at keeping your
resolutions than I am!
R

0
Comment actions Permalink

Vladislav Kaznacheev wrote:

This means more issues will be moved to IDEA Backlog or closed as "Won't
fix". It might be not the nicest fate for an issue, but if we know we
are not going to implement something soon (or ever), we would rather
tell you the truth.


As long as you do tell the reporter something, that's perfectly OK and in any
case better than the uncertainty if there's no response at all. Any effort to
change that is really appreciated.

Sascha

0
Comment actions Permalink

Sorry, but have you read the message to the end?


Sorry, you are right.

At least for the past I often had the feeling, that if an issue was moved to
backlog it meant "won't fix in the next few years". Just some examples I
found so far skimming my reported bugs:

http://jetbrains.net/jira/browse/IDEABKL-2892
http://jetbrains.net/jira/browse/IDEABKL-3157
http://jetbrains.net/jira/browse/IDEABKL-3577
http://jetbrains.net/jira/browse/IDEABKL-4826

Please note, I don't talk about RFEs, I'm talking about bugs, which IMHO
should be fixed (relatively) soon, because if stumbling about them from time
to time after having reported them does not increase the confidence in the
product quality.

0
Comment actions Permalink

Do you really stumble across those? Because I can only reproduce IDEABKL-3577, and that is actually more of an RFE than a bug. I you still can reproduce them, it may be a good idea to post a comment to those bugs with a self contained example which shows the problem. A compilable example usually get the bug fixed much earlier, in my experience.

Bas

Message was edited by:
Bas Leijdekkers

0

Please sign in to leave a comment.