How to query current version

I want to create a search "all open issues in the version we're currently working on".
I have several versions: 0.1 (archive), 0.2 (released), 0.3, 0.4.
So "0.3" is "current version" - a unreleased version which goes after last released version.
Is it possible?
8 comments
Comment actions Permalink
Hello Shike,

Here is the query regarding your request:

project: YouTrack Affected versions: 4.0 #Open
prettyPrint();

In this example "Youtrack" is the name of your project, "4.0" is the number of version which was affected, "#Open" is the state.


You are welcome to contact us if have any questions.
Thank you.
0
Comment actions Permalink
Thanks. But version is explicitly specified in the query. I'd like to have query which automatically picks the current version.
Like:
Fix versions: #Current
prettyPrint();
where "current" is first unreleased version.
0
Comment actions Permalink
Hi Shrike,

It's not quite clear how would like to define the "current" version. In general we can create a workflow which can get the last version in the "Affected version's" bundle (or second version) and call it "current version". The negative of this pattern is that "current version" defines by its place in the bundle (i.e. if your real current version will be on the third place in the bundle, the workflow will work incorrectly).

Thank you,
Waiting for details from you.
0
Comment actions Permalink
Shrike,

I'd like to add the details about the workaround with the workflow.
You can create a custom field called "Current version". Then, when you create an issue, you fill a "Fix version" field with the needed version. Workflow will be automaticaly set the same version in the field "Current version". After that you'll be able to search issues by the "Current version" field.

Also, please note that you can create this saved search:
project: YouTrack Affected versions: 4.0 #Open
prettyPrint(); and share it with all your team. For that please enater the query in search bar and click plus button, navigate to saved query in "Saved searches" -> "Edit"-> configure the visibility of this saved search.
In this case you will update it only once for all users in your team.

Thank you.
0
Comment actions Permalink
Hardcoding index in the bundle for current version isn't a good idea for me.
There should be a simple way to get "current version".
I believe it's a must have feature. Every project which uses "version" notion has a version to be released next, i.e. "current version", version is currently being developed.
0
Comment actions Permalink
Shrike,

I'll reply here to save the order of messages.

Your case is suitable, but it's still unclear what is the criteria of a "current version".
Please take a look at the workaround with the next workflow, I've  suggested above (http://forum.jetbrains.com/message/YouTrack-889-4)  and at the case with the saved search.

Thank you.
0
Comment actions Permalink
Shrike,
Your point is clear. Here's a feature request we've created: JT-19025.
Please feel free to comment or vote to get it implemented faster.

Regards,
  Alexander
0
Comment actions Permalink
Exactly! Thanks. Voted.
0

Please sign in to leave a comment.