Make trac ticket properties more accessible in the Edit/Create Ticket screen

[ericlewis]

In the recent focus overhaul, I believe Focuses got a title attribute added to them; now when you hover over a focus, you get the description for the focus. This is minute and probably unhelpful to the advanced involved core contributor, but super helpful for a person with what a focus actually represents.

This makes me think: how else can we improve the UX of the ticket property editor?

What if we added title attributes for ticket property labels? Hovering over "Version:" could reveal "The earliest WordPress version in which this bug can be reproduced." Hovering over "Milestone:" could reveal "The version this ticket is currently slated to be completed by. Can only be set by core committers and bug gardeners."

I would also dig if component descriptions were discoverable here too.

[nacin]

I'd definitely like to make this better.

I think in an ideal world, someone builds an HTML/CSS/JS mockup of an ideal "new ticket" creation form (let's start there, perhaps, then adopt it for editing). It could then be implemented. But think outside the "Trac" model, first. (Technically, new tickets don't even need to go through Trac's interface. They could be created through an API hit.)

The new ticket form (when you don't have bug gardener privileges) is already very much stripped down. Also, this appears under Version: "If you're filing a bug against trunk, choose 'trunk'. Otherwise, choose the earliest affected version you tested." I've noticed an improvement in version value quality.

[nacin]

In 1071:

Trac JS: Allow wpTrac.nonGardeners() to be manually called by bug gardeners so they can see what most users see. see #360.

[tellyworth]

It's been 4 years without any activity here. It's a good suggestion, but at this point it probably needs to be a factor included in a future redesign or replacement of Trac rather than a forgotten ticket.