Resolved RSS Feed In Jira

http://www.jetbrains.net/jira/secure/IssueNavigator.jspa?view=rss&pid=101
32&statusIds=5&statusIds=6&resolutionIds=1&resolutionIds=2&resolutionIds=
102&sorter/field=issuekey&sorter/order=DESC&tempMax=500&reset=true&decora
tor=none&os_username=[your user name]&os_password=[your password]

This looks for any resolution and status which is closed, fixed, won't
fix, obsolete, and will return 500 issues at a time on one page. Just
modify the user name and password for what you're looking for.

http://www.jetbrains.net/jira/secure/IssueNavigator.jspa?view=rss&pid=100
80&statusIds=1&sorter/field=updated&sorter/order=DESC&tempMax=500&reset=t
rue&decorator=none&os_username=[your user name]&os_password=[your
password]

This is for a current list of the latest 500 Feedback issues.

of course this doesn't resolve the issue of having to search across 3
different categories (which seems to be how JB set things up).

What is curious... Why did JetBrains setup all the software they write
under one big project? Why not have one project for each software? If
you did that, if I understand this crazy interface, then you would have
the IDEA Project with 3 categories, old stuff, dev stuff and feedback
stuff. Then when we do a quick search or search in the Project, we hit
all categories at the same time.

Is it just me or am I misunderstanding something?

Thanks
R

1 comment
Comment actions Permalink

Robert S. Sfeir wrote:

What is curious... Why did JetBrains setup all the software they write
under one big project? Why not have one project for each software? If
you did that, if I understand this crazy interface, then you would have
the IDEA Project with 3 categories, old stuff, dev stuff and feedback
stuff. Then when we do a quick search or search in the Project, we hit
all categories at the same time.


I accidentally hit reply instead of followup when I replied to this
earlier.

Anyway, I agree with what you say here, however, if they used categories
they'd be loosing the ability to use categories for well - categories,
and being able to assign an issue against j2ee, or plugins, or jsp is
good.

One alternate solution is a project level custom field of the combobox
type, offering the three assignments. One apparant problem with this is
the perception that custom fields can't be queried.

I've found this is often the case with project level fields, simply
because the initial query screen is set to "all projects", so it only
shows fields common to all projects; once IDEA has been selected as a
project the page is reloaded (much to some peoples dislike) with project
specific fields available for query.

A third solution would be to have 3 versions defined identifying the
version of IDEA the issue is scheduled to be fixed in (i.e. what we
want, and how jira versions are to be used).

It's been mentioned before that setting up a version called "next build"
and assigning all fixed issues against this, then renaming it with the
build number when released ( and created a new "next build" version ),
but as well as this, you could define versions for "planned",
"ifwegettime" "mostlikelynever".

Thoughts?

Mark

0

Please sign in to leave a comment.