How to file issues? JIRA or Tracker?

Now that the JIRA tracker is up, should we use the ITN Tracker or the JIRA to report issues?

9 comments

Also, what is the address of the RSS feed for Jira?

Norris Shelton
Sun Certified Java Programmer




Keith Lea wrote:

>Now that the JIRA tracker is up, should we use the ITN Tracker or the JIRA to report issues?

>

0

Thunderbird says it is not a valid RSS feed. Bah.

Norris Shelton
Sun Certified Java Programmer




Marcus Brito wrote:

>For the "Recently Added" filter:
>
>http://www.jetbrains.net/jira/secure/IssueNavigator.jspa?view=rss&pid=10080&createdPrevious=604800000&sorter/field=created&sorter/order=DESC&tempMax=25&reset=true&decorator=none
>
>Just select any issue filter and click on 'XML' above the table -- this will be the RSS view for that filter.

>

0

Marcus Brito wrote:

For the "Recently Added" filter:

http://www.jetbrains.net/jira/secure/IssueNavigator.jspa?view=rss&pid=10080&createdPrevious=604800000&sorter/field=created&sorter/order=DESC&tempMax=25&reset=true&decorator=none


As I mentioned in another thread, you'll need to add
os_user=xxx&os_password=xxx to the URL as well, -if- the feed in
question hits anything requiring authentication.

0

Keith Lea wrote:

Now that the JIRA tracker is up, should we use the ITN Tracker or the JIRA to report issues?



Can somebody from jetbrains answer that question please?

Should we only report Irida bugs to JIRA or all new bugs?

Mike

0

Guessing by the long response time, I think they want to say "Yes, please use JIRA", but aren't totally confident about that yet.

In my humble opinion, there are a few necessary tweaks to make the JIRA install as useful as the current tracker, like preserving links to old issues and message formatting (the latter being my pet peeve). I guess they'll also modify the automatic bug reporting dialog to send data to JIRA. Till there, we're supposed to keep filing issues in the current tracker.

That being said, I recently I've filed a couple of issues on JIRA, and got prompt response from JetBrains people -- I think this means the new installation is being used and watched, and it's just a matter of time before the old data from the ITN tracker is moved.

0

Well, the problem acually is as follows:
Old tracker as well as current Jira installation both serve two different
functions at the same time:
1. Got more or less structured response from the community
2. Provide the team with structured plan of what should be done/implemented/fixed
etc.

Tracker usage practice shows that those two functions aren't the same and
may even contradict each other as user requests do not specify concrete items
of work to be done. They often highlight the problems users might have when
working with IDEA because of missing functionality while feature implemented
to cover the missing piece might be quite different from what's been suggested.
This way the situation some feature request is being closed as fixed while
the functionality being requested by the user wasn't actually implemented.
Not good.

I remember the times there were no tracker open to public and all the feature
requests were discussed in mailing list prior implementation. While this
kind of cooperation seem much more straightforward and effective it's not
an option anymore whith such a community size we have right away.

The other option would be let say have 2 Jira installation but I'm affraid
that synchronization would be quite a painful task while separating the team
from the community even more.

What do you think?

0


What do you think?


I kind of like putting my bugs in Jira now, hope I'm not doing something
wrong, and seeing who it's assigned to and what its status is.

R

0

something wrong, and seeing who it's assigned to and what its status


It's all right for sure.

0

Please sign in to leave a comment.