Making WordPress.org

Opened 10 years ago

Last modified 6 years ago

#499 new enhancement

Trac nav menus should be consistent across all WP.org Tracs

Reported by: sergeybiryukov's profile SergeyBiryukov Owned by:
Milestone: Priority: normal
Component: Trac Keywords:
Cc:

Description

Core Trac doesn't have a "New Ticket" link on internal pages, it only has an icon on the right (I spent a few minutes looking for it for the first time).

Other Trac instances, however, don't have that icon, and still have "New Ticket" link instead.

The workflow for creating a new ticket should be consistent across all our Trac instances.

Attachments (1)

meta-499.png (43.0 KB) - added by SergeyBiryukov 10 years ago.

Download all attachments as: .zip

Change History (13)

This ticket was mentioned in IRC in #wordpress-meta by sams. View the logs.


10 years ago

#2 follow-up: @melchoyce
10 years ago

  • Keywords ux-feedback added

I don't know if it's just the icon choice, or the lack of label or what, but even though I'm used to adding tickets semi-regularly I always have to hunt for the new ticket icon on core trac. Can we add a label to it?

#3 in reply to: ↑ 2 @DrewAPicture
10 years ago

Replying to melchoyce:

I don't know if it's just the icon choice, or the lack of label or what, but even though I'm used to adding tickets semi-regularly I always have to hunt for the new ticket icon on core trac. Can we add a label to it?

FWIW, I agree about maybe adding a label. More often than not, I just go directly to /newticket in the URL bar, because I always have trouble picking out the icon.

#4 @nacin
9 years ago

I added "New Ticket" to the nav. It's ugly, but it works.

#5 @SergeyBiryukov
9 years ago

Why don't we make the nav menu (Timeline / New Ticket / ... ) consistent across all WP.org Tracs?

#6 @ocean90
9 years ago

-1 on adding the "New Ticket" to core Trac. The nav got removed in favour of the icons and our component pages.

The is already a button on the search results page, on each component page, on https://make.wordpress.org/core/reports/ and, well, there is the icon.

In my opinion we shouldn't make it that easy to create a new ticket without letting people digging a bit around so they get familiar with the Trac system. New visitors should figure out first that core Trac isn't a ticket system for support.

#7 @SergeyBiryukov
9 years ago

  • Summary changed from "New Ticket" links should be consistent to Trac nav menus should be consistent across all WP.org Tracs

It's not just "New Ticket", "Browse Source" and "Timeline" links should be consistent as well. Renaming accordingly.

#8 @samuelsidler
8 years ago

We'll be reworking the nav design when bringing O2 across (and updating the trac themes). We can probably make things more consistent in the process. See #1821.

#9 @magicroundabout
8 years ago

My UX feedback carried over from #1858

I was at a WordPress Contributor day today. I've contributed before, but it's not a frequent occurrence. Consider me a relative newbie.

On https://core.trac.wordpress.org/ there's a big blue new ticket button. I expected to click "Tickets" in the nav and then "New ticket" somewhere. It really wasn't clear at all. The meaning of the small icon is not clear either. You guys probably know what it does, but a new contributor doesn't.

@ocean90's comment about not wanting people to treat Trac as a support system is validity. So there's an interesting UX question about how you raise the barrier to entry, but without making life unnecessarily hard for people who do want to contribute but are inexperienced with Trac. On another day with less time I might have walked away in frustration.

If you're reviewing the whole nav then I'm happy to be involved. It's pretty confusing. Two search options that do different things, paths that lead to similar-but-different screens. If you want a relatively new trac user to give feedback, feel free to look me up on Slack.

Thanks

Version 0, edited 8 years ago by magicroundabout (next)

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


6 years ago

#11 @karmatosed
6 years ago

  • Keywords ux-feedback removed

It looks like a lot of unifying has happened across tracs. For now removing ux-feedback as seems alignment has taken place at least in part.

#12 @tellyworth
6 years ago

#1858 was marked as a duplicate.

Note: See TracTickets for help on using tickets.