JB - What's happening with the backlog?

Robert Gibson wrote:

Should I just abandon any hope of seeing my old feature requests ever
implemented or my old bugs fixed?

From what I understand, during the move to JIRA any old items that were
going to be implemented in Irida were moved to IDEADEV and any old items
that would have to wait until a later version were moved to IDEABKL.

As new requests come in, many of them are related to bugs in the new
features being added to Irida or related to specific points in the
functionality that is already being planned (such as specific features
in HTML and JSP which is one of the focuses for Irida), and therefore
many of those items are moved directly to IDEADEV. Other items that
don't fit into the plans for Irida will have to wait until a future
version and are moved to IDEABKL.

Once Irida is done, I expect Jetbrains to take a new look at IDEABKL and
move some of those items into the new IDEADEV for the next EAP. But
until then, the previous "judgement" is still valid.

(Have I misunderstood or missed anything? I'm not employed by Jetbrains
or anything, this is just the way I've interpreted what's going on with
the bug lists.)

You're quite right Jonas. One thing I'd like to add is we wouldn't mind to
get a reminder postings here in eap forums regarding those issues in backlog
if someone thinks some of those issues need to be worked on before Irida
ships.

-

Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"

Robert Gibson wrote:

>> Should I just abandon any hope of seeing my old feature requests ever
>> implemented or my old bugs fixed?
>>

From what I understand, during the move to JIRA any old items that
were going to be implemented in Irida were moved to IDEADEV and any
old items that would have to wait until a later version were moved to
IDEABKL.

As new requests come in, many of them are related to bugs in the new
features being added to Irida or related to specific points in the
functionality that is already being planned (such as specific features
in HTML and JSP which is one of the focuses for Irida), and therefore
many of those items are moved directly to IDEADEV. Other items that
don't fit into the plans for Irida will have to wait until a future
version and are moved to IDEABKL.

Once Irida is done, I expect Jetbrains to take a new look at IDEABKL
and move some of those items into the new IDEADEV for the next EAP.
But until then, the previous "judgement" is still valid.

(Have I misunderstood or missed anything? I'm not employed by
Jetbrains or anything, this is just the way I've interpreted what's
going on with the bug lists.)

So, isn't adding comments to the backlog issues enough to raise your
awareness? I recently updated
http://www.jetbrains.net/jira/browse/IDEABKL-2866
thinking it was worth making it into 5.0 but never got a sign telling me
that
one of you had reconsidered the issue.

Thanks,

Vince.

Yep, I've read your comment there Vince. However it appears we need to perform
serious architectural refactoring to get it working thus we've decided to
postpone those until Irida ships.

-

Maxim Shafirov
http://www.jetbrains.com
"Develop with pleasure!"

So, isn't adding comments to the backlog issues enough to raise your
awareness? I recently updated
http://www.jetbrains.net/jira/browse/IDEABKL-2866
thinking it was worth making it into 5.0 but never got a sign telling
me
that
one of you had reconsidered the issue.
Thanks,

Vince.

Maxim Shafirov (JetBrains) wrote:

You're quite right Jonas. One thing I'd like to add is we wouldn't mind
to get a reminder postings here in eap forums regarding those issues in
backlog if someone thinks some of those issues need to be worked on
before Irida ships.

Though this isn't a show-stopper, I'd like to see this fixed before it's going
to celebrate its 2nd anniversary:
http://www.jetbrains.net/jira/browse/IDEABKL-1092

There's also this one that can be annoying when you're getting used to press
ctrl-shift-enter everywhere:
http://www.jetbrains.net/jira/browse/IDEABKL-1239

And, if there's any chance, editing Ant files would get such a nice improvement
with this one:
http://www.jetbrains.net/jira/browse/IDEABKL-2350

Sascha

PS: I know, those don't need to be fixed, but I have a feeling they would end
up in IDEADEV if they were entered today ;)

Well I don't generally post tracker items unless I think something
should be fixed!

- Personally I think any false positives or negatives in code analysis
("bad code green"/"good code red") should be fixed. E.g. (just some
from my watchlist)
http://www.jetbrains.net/jira/browse/IDEABKL-995
http://www.jetbrains.net/jira/browse/IDEABKL-1312
http://www.jetbrains.net/jira/browse/IDEABKL-1324
http://www.jetbrains.net/jira/browse/IDEABKL-1843

- I heard that the JSP parser was getting a revamp, but my biggest JSP
bug is still in BKL http://www.jetbrains.net/jira/browse/IDEABKL-381

- And it's just a little low-priority feature request, but I would love
this one :) I'm always playing with variable declarations and it's much
more of a pain than it should be:
http://www.jetbrains.net/jira/browse/IDEABKL-1404


I could go on, but I don't know if making noise about them is going to
make anything happen apart from annoying the team that's making the best
IDE I've ever used ...
R

Here's some more, the password related ones are actually quite critical:

http://www.jetbrains.net/jira/browse/IDEADEV-239
- http://www.jetbrains.net/jira/browse/IDEABKL-1952
- http://www.jetbrains.net/jira/browse/IDEABKL-1967

With these "Submitted (Assigned)" ones you never know if they fell
through a crack or not. Here's a little bump for some:

http://www.jetbrains.net/jira/browse/IDEABKL-2631
http://www.jetbrains.net/jira/browse/IDEABKL-2317
http://www.jetbrains.net/jira/browse/IDEABKL-540

Sascha