Using the bulk update feature of JIRA I did the following operations based
on some JQL filters.
Remove the 4.0.0 tag from the following:
* project = hive and (status = Resolved or status = closed) and (fixVersion
= 4.0.0-alpha-1 or fixVersion = 4.0.0-alpha-2)
Clear fixVersion from the following l
Thanx Stamatis for volunteering. I think we should delete the 4.0.0-alpha-2
version from the Jira as well to prevent people from carelessly using that.
There is an option here[1] to delete a version, can give a try like if just
deleting the 4.0.0 also from this list helps or not.
[1]
https://issu
No script at all, I am just going to use the "Bulk Update" feature in JIRA.
I will wait 24h in case there are objections and then move forward with the
update.
Best,
Stamatis
On Thu, Oct 20, 2022 at 12:12 PM Denys Kuzmenko
wrote:
> Hi Stamatis,
>
> If you have an automatic script for that plea
Hi Stamatis,
If you have an automatic script for that please run it.
Note, I saw tickets with `fixVersion = 4.0.0 and fixVersion =
4.0.0-alpha-2` in resolved state as well.
https://issues.apache.org/jira/browse/HIVE-26643?jql=project%20%3D%20HIVE%20AND%20status%20%3D%20Resolved%20AND%20fixVersion
Hi everyone,
The past discussions around the version used in JIRA can be found in the
following threads [1, 2].
As Ayush mentioned there are ~3K resolved tickets with Fix Version 4.0.0
but most of them are also tagged with 4.0.0-alpha1 [3].
I can easily remove the 4.0.0 tag from those tickets an
Hi Denys,
Flaging the version stuff here what we discussed offline.
The version 4.0.0 was used prior the decision to rename it 4.0.0-alpha1 was
taken, but the rename was not done on the Jira.
It still shows around 3K tickets resolved on version 4.0.0, which got released
already as part of the l
