Also, @jhurwitz the reason we think the icons are cool is because "blocker" is probably more a status than a priority, or at least it mixes well. You could have a high priority blocker and a low priority blocker, and give them a cool icon like .

Oh, right. Sorry, I'm being totally unhelpful here and conflating priority and status.

Let me verify / fix any color sync issues, and you might get this for free. :)

we let you pick icons for maniphest.status, but it doesn't display on workboards.

Ummmm, I want to say no, that the icon color and the bar color are not fully in sync.

I think we're also going to let you pick different icons, that's just blocked on me actually doing that.

Actually, I just saw that you switched from .phui-object-item-bar-color-red to .phui-icon-view.red. It looks like we now have 14 color options; that's probably good enough for us for now.

We have 7 priorities (one more than the default). Our new priority is "Blocker!", which we put in between High and Needs Triage.

It looks like icon is configurable per *status*, but I'm looking for a way to differentiate per *priority*.

Also, barColor does not exist in master, we use icon + color now to convey information instead of just color (and yes, icons are configurable for Maniphest).

We'll give you a badge if you complete the task. The problem is easy tasks are easy, so we just usually do them.

Lol

Well, due to recent shortages of warm expressions of user gratitude, the upstream has had to resort to providing their own positive feedback. They achieve this by self-awarding cool-looking badges for commits.

What does Badge Awarded mean?

I'm so stoked about all these badges I'll be getting.

Going to assume you just want it easier to work through a list of stuff.

Our general policy is we don't take bug reports or support requests on prototypes (as in, they are known to be buggy and incomplete). I consider that more "loose rule" and not a hard guideline, certainly we want to fix things that might cause your company issues.

Is it worth filing these bugs in the future, or should I hold back?

(and they are not kept "production ready")

I think we should move UIExamples to a prototype, as they are only useful if you develop Phabricator.

What are you trying to accomplish?

We only convey this information through the use of color, which could also cause difficulty for users who do have vision problems.

https://secure.phabricator.com/book/phabcontrib/article/feature_requests/#describe-problems

This problem is happening for both the notification popup as well as the dedicated notification page.

I didn't get as far as implementing this, but my intention was to make clicking the token eventually take you to the object's page (for example, the project's detail page or the user's profile page), not select the token.

T4863 would be the task to follow for adding additional information to cards in Workboards. I'm not convinced adding more colors solves any underlying problem in the product - it also creates a bit of a problem in accessibility (which is why we moved away from barColors to begin with). Can I ask what specifically are all the priorities you use and what they're for? Do you expect all users to understand so many colors and what they mean? Are they implemented consistently?

At a glance, in views that don't otherwise indicate priority (eg, workboard with natural sort order), I'd like to be able to visually distinguish between all of our different priorities.

Can you go into more detail about your specific problem. What information are you trying to convey?

In T8885#126858, @chad wrote:

Also, #phui is the best tag for these, which is "Phabricator UI". Maybe a good way to think about it is #design is pre-commit, #phui is post-commit. :)

Actually, I might have a way to make these work in the mobile/button case.

Also, #phui is the best tag for these, which is "Phabricator UI". Maybe a good way to think about it is #design is pre-commit, #phui is post-commit. :)

Yeah, I had left it open in case of feedback, but I've been using (larger font) for a while and it works great. I'll just have one minor diff on Conpherence menus.

I think this is covered, now?

They're cached: when you update a Postprocessor without touching CSS, that doesn't dirty the caches, so this server still has a cached version of my old colors. It'll fix itself eventually, but I can look at making it smarter.

@epriestley, the high contrast boxes here are purple, but are not in my sandbox. Can't figure a reason why.

I would propose that we make this task into: Prefetch/cache 50 users and 50 projects for the typeahead.

Re-running my experiment (typing two characters at a time), AJAX calls are now taking 700-1000 ms.