joomla
[Question] Build field not very UX friendly.
Using the Issue Tracker interface, the Build field is required but there's no explaination (at least in fr-FR) about its purpose and users are able to fill in what ever he want, here: "je rentre ce que je veux dans ce champ" and it works.
Maybe a tooltip is needed and/or a way to select the version concerned ?
There have been oh so many discussions about this "build" field since the old joomlacode.org tracker, the only consensus being that nobody knows what to do with this field since it was never used, but it has to stay for some reasons. IIRC the last time talking about those fields the "easy" option was added, and we even ported this silly thing (to me) to the new tracker...
Maybe JBS can confirm that the "build" field is no longer in use so we can remove it.
It's supposed to be a place you put an affected version of whatever software. Most just put it right into the issue report though so it's honestly extra cruft at this point I'd say. Since it's a free text field and not a select list it's not like it's something you can easily run reports or filters against.
it is more useful in the context of the CMS tracker than it is here on the issue tracker
On 9 August 2016 at 13:32, Michael Babker [email protected] wrote:
It's supposed to be a place you put an affected version of whatever software. Most just put it right into the issue report though so it's honestly extra cruft at this point I'd say. Since it's a free text field and not a select list it's not like it's something you can easily run reports or filters against.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/joomla/jissues/issues/856#issuecomment-238538591, or mute the thread https://github.com/notifications/unsubscribe-auth/ABPH8brd2MS6qSh03R2132RD8xBj8wkdks5qeHNzgaJpZM4Jb1RN .
Brian Teeman Co-founder Joomla! and OpenSourceMatters Inc. http://brian.teeman.net/
It's useful on all of the projects except the issue tracker but we're lacking CCK-esque functionality to define the issue form per project.
Any other thoughts here? More of me leans toward dropping it than keeping it.
