Where can you see version IDs mapped to their "friendly names"?

[BobbieD]

I wonder if anyone knows of any shortcuts or more elegant alternative to this pretzel logic I currently perform when I update filters:

Since I use the advanced filter, and the advanced filter uses Version IDs instead of Version names, I can’t just select or type the newly added versions, because:

1) I don't know the arbitrary reference # that JIRA assigns to any new version created, and

2) The comma-separated list of Version IDs I already have included in my filter isn't something I can look at and say, "oh, I see the latest version I have included is 2.3.2, so I need to type "2.3.3" to prompt the auto-fill". Even if I DO know enough to prompt the auto-fill, and even if I find the version I think I need, I won't know if it was one of the version IDs I already had in my filter because the query string only displays the version name that I typed.

3) I can’t switch to simple searching to get these either, because my query is too complex.

So what I do is create a new filter with the simple search, select all of those versions, then click to the Advanced option to view their reference numbers.

Then I paste those numbers into a spreadsheet, and sort them against the reference numbers that I already have.

Then I back out of that fake new filter creation task, and open up the existing filter, and enter the reference #s for the new versions I’m adding.

I tried looking at the Versions page for the project, but the reference numbers are not mapped to the version names, and don’t appear in the linking URL.

It really seems like the Version IDs should appear in a column on the project's versions page.

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

I am sure it is better if it is listed as a different column but there is an option to find it. Browse the project, go to Versions and click on the version. it will take you to the 'Browse Version' page. You can find the id at the end of the url. Something like:

https://localhost:8080/browse/PKEY/fixforversion/10001

[BobbieD]

Thanks, this is a step better than I had, but as you noted, not ideal.

[BobbieD]

Our company creates versions that are not just numbers, but contain dates and relational information. Here is an example:

2.1.10 (code cutoff 31-jan-2011,tag date 31-Jan-2012)

So when creating a filter that has multiple versions in it, it resolves to the IDs, not the quoted names. Then that filter is copied and altered slightly to add or remove different versions. It's come to the point where I use a Confluence page to reference which ID is mapped to which release. Really dumb. This ought to just be listed on the versions page, as a separate column.

[tier-0 grump]

I'm a little confused - the advanced search supports version names - by default it works with id's but it supports names just fine. It may give you strange results if you don't constrain it to a project (as you can have version 2.4 in multiple projects) which is why an id search is often better - the only reason the advanced search gets populated by an id when switching from simple to advanced is because we have undertaken the search using the id.

[tier-0 grump]

I'm a little confused - the advanced search supports version names - by default it works with id's but it supports names just fine. It may give you strange results if you don't constrain it to a project (as you can have version 2.4 in multiple projects) which is why an id search is often better - the only reason the advanced search gets populated by an id when switching from simple to advanced is because we have undertaken the search using the id.