WEB-929bugs.mojang.com does not allow Affected Version search from previous snapshots
It appears that versions that have been marked as archived cannot be searched using Basic search. Please use Advanced search if you want to search for older versions.
This functionality is not something that we can change, it is restricted by Jira which is the platform we built the bug tracker on.
Could someone allow us to also search for previous snapshots of the same version in the "Affects Version" Advanced search?
Because I have searched for any bugs related to 'some subject' on the latest snapshot, I'd love to include previous versions in the search, but it won't allow me to select any besides the very very latest snapshot, this makes searching for bugs to prevent duplicate tickets more difficult.
If time wasn't such an issue, I would take 10 minutes to search for a bug, instead of checking the latest and only available for search version.
For example, if I search for version 17w45b as of now, it will show up, but if I search for 17w45a or 17w43b or 17w43a, it won't show up. Which makes finding bugs that have been found, but not been updated to be affecting recent versions to show up.
Usually searching for certain criteria will bring up a huge list of bugs, some which have been fixed, some which are only related.
Going through this list takes a bunch of time, as well as usually you know that it can only have been an existing bug since some version x in the past. So you'd like to check all versions above version x, for that bug. Usually including too much information in the search bar will block your query from being found, because people describe the bug in a different way as you would.
take "kick command fails and breaks game" vs "Executing /kick <target> on a single player world, will result in crash."
Therefore me searching for "kick single player" won't allow me to find the previous.
While if I only searched for "kick", there would be a huge load of bugs coming up from ancient versions.
This is why I am posting this, I would love to reduce the amount of duplicate tickets, as it also takes us time to create such a ticket. Aiming for a better experience in game and on the bugtracker!
- Hugs Melvin
NormalCreated Issue:
bugs.mojang.com does not allow Affected Version search from previous snapshots
Could someone allow us to also search for previous snapshots of the same version in the "Affects Version" Advanced search?
Because I have searched for any bugs related to 'some subject' on the latest snapshot, I'd love to include previous versions in the search, but it won't allow me to select any besides the very very latest snapshot, this makes searching for bugs to prevent duplicate tickets more difficult.
If time wasn't such an issue, I would take 10 minutes to search for a bug, instead of checking the latest and only available for search version.
For example, if I search for version 17w45b as of now, it will show up, but if I search for 17w45a or 17w43b or 17w43a, it won't show up. Which makes finding bugs that have been found, but not been updated to be affecting recent versions to show up.
Usually searching for certain criteria will bring up a huge list of bugs, some which have been fixed, some which are only related.
Going through this list takes a bunch of time, as well as usually you know that it can only have been an existing bug since some version x in the past. So you'd like to check all versions above version x, for that bug. Usually including too much information in the search bar will block your query from being found, because people describe the bug in a different way as you would.
take "kick command fails and breaks game" vs "Executing /kick <target> on a single player world, will result in crash."
Therefore me searching for "kick single player" won't allow me to find the previous.
While if I only searched for "kick", there would be a huge load of bugs coming up from ancient versions.This is why I am posting this, I would love to reduce the amount of duplicate tickets, as it also takes us time to create such a ticket. Aiming for a better experience in game and on the bugtracker!
- Hugs Melvin
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
Mojang Studios NoteIt appears that versions that have been marked as archived cannot be searched using Basic search. Please use Advanced search if you want to search for older versions.
This functionality is not something that we can change, it is restricted by Jira which is the platform we built the bug tracker on.
Could someone allow us to also search for previous snapshots of the same version in the "Affects Version" Advanced search?
Because I have searched for any bugs related to 'some subject' on the latest snapshot, I'd love to include previous versions in the search, but it won't allow me to select any besides the very very latest snapshot, this makes searching for bugs to prevent duplicate tickets more difficult.
If time wasn't such an issue, I would take 10 minutes to search for a bug, instead of checking the latest and only available for search version.
For example, if I search for version 17w45b as of now, it will show up, but if I search for 17w45a or 17w43b or 17w43a, it won't show up. Which makes finding bugs that have been found, but not been updated to be affecting recent versions to show up.
Usually searching for certain criteria will bring up a huge list of bugs, some which have been fixed, some which are only related.
Going through this list takes a bunch of time, as well as usually you know that it can only have been an existing bug since some version x in the past. So you'd like to check all versions above version x, for that bug. Usually including too much information in the search bar will block your query from being found, because people describe the bug in a different way as you would.
take "kick command fails and breaks game" vs "Executing /kick <target> on a single player world, will result in crash."
Therefore me searching for "kick single player" won't allow me to find the previous.
While if I only searched for "kick", there would be a huge load of bugs coming up from ancient versions.This is why I am posting this, I would love to reduce the amount of duplicate tickets, as it also takes us time to create such a ticket. Aiming for a better experience in game and on the bugtracker!
- Hugs Melvin
![[Mod] Pokechu22](../../../data/avatars/users/92931.png){kind=small}
I see the problem you're having. On the basic search, for Affected Versions, it only lists current versions, and refuses to allow older versions (which are archived).
However, it does work on the advanced search – try querying affectedVersion = "Minecraft 14w20a" (the quotes and Minecraft are required, as affectedVersion does not support fuzzy-matching with ~).
I'll check if it's possible to enable this for the basic search (it seems strange that it lets you look through affected versions but limits you to recent ones).
Thanks, at least that is a decent work around I guess.
But if you have a better way to concat versions than:
affectedVersion = "Minecraft 17w43a" OR affectedVersion = "Minecraft 17w43b" OR affectedVersion = "Minecraft 17w45a" OR affectedVersion = "Minecraft 17w45b"
I'd gladly like to know.
affectedVersion IN ("Minecraft 17w43a", "Minecraft 17w43b"......)
Yes, I figured it out, but thanks regardless!
Yep:
affectedVersion IN ("Minecraft 17w43a", "Minecraft 17w43b", "Minecraft 17w45a", "Minecraft 17w45b")
You can also do this:
affectedVersion > "Minecraft 1.12.2"
I found JRASERVER-31534 that makes it look like the basic search should support that, but it doesn't work here. Not sure why, since we should be running a version with that fix. (I've also found JRASERVER-27596 but that doesn't apply here)
It sounds like before JRASERVER-31534 was fixed, basic search did not work for projects with archived versions at all. I can confirm basic search does not work with archived versions, for any of our projects.
Mojira is built on a platform called Jira and these fixes cannot be resolved by us but by the software developers. I'll close this bug as there is nothing that Mojang can do to fix it, but if you'd like to have it fixed I suggest you report it directly to Atlassian and the Jira team here.