Re: Remember to correctly set the fixVersion when resolving tickets…

2021-01-11 Thread Berenguer Blasi
Thanks Mick. I had no particular query in mind. It's just some Jira JQL sugar I'd thought I'd share. This would allow you to see which tickets were tackled during beta phase i.e (fixVersion >= beta1 AND < RC) without having to specify each version individually building a super long JQL. Also newly

Re: Remember to correctly set the fixVersion when resolving tickets…

2021-01-10 Thread Mick Semb Wever
Interesting Berenguer, thanks for pointing that out. I had recently ordered those unreleased versions to put the placeholders first in the list and then the real versions second, but otherwise in order as you describe. The queries you desire then should work, so long as they are bound to either r

Re: Remember to correctly set the fixVersion when resolving tickets…

2021-01-10 Thread Berenguer Blasi
If an admin drag&drops the jira versions up/down in the correct order in that screen, then we could jql like: 'fixVersion >= 4.0 AND fixVersion < 5.0' and similar sorted/range queries which is quite handy when building up jql queries. My 2 cts. On 4/1/21 9:18, Mick Semb Wever wrote: > For jira hyg

Remember to correctly set the fixVersion when resolving tickets…

2021-01-04 Thread Mick Semb Wever
For jira hygiene, the current precedence is that resolved tickets do not keep their placeholder fixVersions. For example, no resolved ticket should have a fixVersion of 3.0.x, 3.11.x, 4.0-alpha, 4.0-beta, 4.0-rc, or 4.0.x. And… all 4.0-alphaX and 4.0-betaX resolved tickets should have the addition