New version of JIRA

I haven't seen this mentioned here, but it seems they have upgraded to
JIRA 3.3, which means we can finally search for issues in multiple
projects (IDEA + IDEADEV + IDEABKL), and we can search for issues fixed
within a range of build numbers, not just in a single build!

0
4 comments
Avatar
Permanently deleted user

Jonas Kvarnström wrote:

I haven't seen this mentioned here, but it seems they have upgraded to
JIRA 3.3, which means we can finally search for issues in multiple
projects (IDEA + IDEADEV + IDEABKL), and we can search for issues fixed
within a range of build numbers, not just in a single build!


Unfortunately we can't search by component. I just filed
http://jira.atlassian.com/browse/JRA-7678 for it.

0
Avatar
Permanently deleted user

Searching across all three projects is nice! That was my biggest issue.

Also, you can now sort on the "Fixed in build" column.
Jetbrains should update the global filter "Fixed in unreleased versions" so that it sorts on "Fixed in buid" column (descending).

Is it now possible for Jetbrains to provide a link showing the issues fixed when they announce a new build?

0
Avatar
Permanently deleted user

Alex wrote:

Searching across all three projects is nice! That was my biggest issue.

Also, you can now sort on the "Fixed in build" column.
Jetbrains should update the global filter "Fixed in unreleased versions" so that it sorts on "Fixed in buid" column (descending).

Is it now possible for Jetbrains to provide a link showing the issues fixed when they announce a new build?


Does this work for you?

http://www.jetbrains.net/jira/secure/IssueNavigator.jspa?refreshFilter=false&reset=update&pid=10132&customfield_10011%3AgreaterThan=3456&customfield_10011%3AlessThan=3459

I have no idea whether refreshFilter=false&reset=update needs to be
there, but they were used as hidden fields in the form so I guess they
have some kind of relevance...

0
Avatar
Permanently deleted user

Yes, that worked!

JetBrains, can you include this in your build announcements?
I think most everyone is interested in seeing what was fixed, and by including the link you'll be saving everyone some time.

0

Please sign in to leave a comment.