Generally, we want to understand problems, which is why I linked the guide to you. A example might be that Team A is "Marketing" and Team B is "Engineering" and the Field is a Select, that uses values X, Y, and Z, and Engineering triages them, but Marketing doesn't need to set them. This tells us a good story at which to understand overarching needs. Upcoming tools like Nuance sit in front of Maniphest and might be what you're looking for, or maybe not, I just don't have enough backstory here.

Sorry, I understood perfectly the feature you wanted. I don't understand the core problem you're trying to solve. If you could get into specifics, it would help us better understand if, for instance, you should just be using Nuance. Can you be more specific and tell us what the field your attempting to us is, for example?

@chad Sorry that I didn't explain that clear enough in the description, here is what I'm trying to accomplish:

ref T9412

That sounds like it might be what's going on. I apologize for not having better steps to reproduce; I'm working backward from example emails that folks are receiving, so it's been a bit of a guessing game as to how to make this happen.

I think I have a pretty good guess about this one.

Can you be more specific about the steps to reproduce?

1. manually restarted php5-fpm and phd services
2. colleague, member of ops submitted review touching src/ansible
3. that review doesn't explicitly list "ops" as blocking reviewers because he's also an owner of ansible, but it does highlight my review in yellow
   
4. he lands it after I accept it
5. his commit is flagged for review despite both of us being members of ops

@joshuaspence, see T11010, I think. Not sure why nginx was 502'ing there, but should be fixed in HEAD.

I will manually restart everything and reproduce again

Before I dig into this, is there any possibility this was a daemon running old code? I don't remember if I tested this explicitly and it could quite reasonably be an upstream bug, but the code at least attempts to check for this, and D15939 theoretically fixed issues with this.

We can also use weird implicit magic to try to resolve this. Here's a ruleset that will make everyone equally confused and unhappy:

That's a lot more clear, thanks!

I think that that creates some tension that I'm not immediately sure how to resolve:

The user story most important to us is:

In T10855#172123, @chad wrote:

A Phriction Panel which we talked about briefly would provide this automagically without wiring Dashboards to Conduit.

We would be okay with this too.

We aren't really sold on this as a specific use case, but can give you a modern dashboard.panel.edit which will let you implement it. If there are weird followups arising from this (like difficulty managing the 300,000 transactions on the panel detail a year from now) we may be somewhat less sympathetic to them than we would be to a more on-label use case.

This is about two hours of work.

There were ultimately two sort of related requests here, although some of the discussion happened off-thread. Let's call them arc diff --draft and arc diff --try:

unfortumately

The time zone selected below has been auto-detected based on your browser settings

This may also be T11015.

Thanks, that's what I'm thinking, too, but I wanted to check all of the options. Thank you.

Or, at least, not one we've ever heard of nor are likely to be able to replicate. Google seems to suggest this is a local computer / network issue.

This isn't a problem with Phabricator.

I tried it out. One thing I realized was that without having the context of this ticket, during the pop-up after you click the notification, it's not obvious whether the timezone being shown is the *current* setting or the *new setting based on your browser*. That could cause confusion, so would suggest a slight phrasing change there.

Yeah, current behavior is garbage. Not sure if I changed it by accident while doing other changes or we just didn't run into it before, but there's no technical or product reason for it to work like it currently does.

I ran into an identical issue (and debugged on chat). Agreed that there could be better messaging around this.

that worked. there's no indication in the UI that the trailing slash is required, the link rendered works fine

I suspect it isn't going to get very far because we lose our ability to optimize lookups (I wrote this in the general case as "regexp", but mean "regexp/wildcard" -- wildcards aren't as complex but I think the general case still holds).

Try /wsl_root/src/ansible/ (with a trailing slash)?

For issues with Ubuntu 16.04 LTS and acpu with PHP7 giving rise to "apc_sma_info() not found" Exceptions then you could install backward compatibility library package php-apcu-bc_1.0.3-2_amd64.deb using dpkg once downloaded from future Ubuntu Yakkety release universe repository. No doubt this deb will get back-ported to 16.04 LTS soon enough assuming phabricator itself isnt updated to no longer reference this missing function.

Please follow all the steps in Contributing Bug Reports. Specifically we need to know how to reproduce the issue locally.

Funny enough there were discussions among the engineering leads on Friday about having this type of functionality in Phabricator being useful. It wasn't a main point of discussion but several did look to Phabricator for being able to solve some concerns. The primary concern was around having accountability for specific quality points which may not necessarily be clear from the revision alone. Without Phabricator we approach this pretty much as I had mentioned above (training materials and KB/wiki with a checklist to be used with some pre-commit unit tests to help with some items that can be automatically checked), however we work in a well-regulated industry where checklists/documents as evidence are often highly valued. I think for the time being if we decide to move forward with this in Phab we may include a "template comment" to be filled out and used when accepting revisions.

Evan, thanks (as usual) for elaborating which options are available! This is very helpful.

I apologize, my ansible deploy script *should* have restarted everything that needs restarting, but it appears it didn't.

General question: Why is the owners option "Add as reviewer (blocking)" if an owner uploads a revision? I know that this is expected, but why? For example at Wikimedia we currently have the system, that every change needs a review from an "owner" before the patch gets merged, so it's not useful, if an owner of the package uploads a change, and no reviewers get added. Maybe the a compromise may be a setting, where you can choose, if a package gets added as reviewer too, if the author of the revision is an owner too? I think that would help all.

The following queries are full table scans:

Yeah I think assignee is an important piece of information, but created seems not that important? And like, in terms of focusing a user's attention, the gutter feels like "this is the second most important thing to title". Like having the avatar of the user who created it doesn't feel like very useful information.

The main challenge here is in Phabricator, tasks are ephemeral wikis that tend to be community built. Knowing the author is generally inconsequential, though here directly we may treat the severity of the task differently if we know which install is filing it. I think assignee is reasonable to highlight, but is not always present. So then do we only show if it's assigned, or have some pointless placeholder text taking up space. We tend to never hide information, so then on this install we'd be stuck with 98% of tasks saying unassigned. It's all kind of lose-lose which is why it's how it is today (which still feels correct for most installs).

Maybe we should just improve curtain first

Actions are always at the top of the sidebar, and pushing them down inst something I want to explore, since it makes day to day use significantly harder, but maybe it wouldn't be as bad as I imagine.

Personally I'm not really sold on the gutter text. It forces everything else down for what could just be positioned at the top of the sidebar?

It's an interesting idea. I'm not super happy about promoting the author as the "important" part of the task / image, but having a nice summary explaining it's full current state seems pretty helpful.

I don't know how to reproduce the issue, but figured I'd let you know that I'm seeing this in our error logs:

Did you restart all webservers/php-fpm/etc. after upgrading? Did you upgrade the storage?
I cannot immediately reproduce this - see Contributing Bug Reports for some more information that can help you.

Did you fully restart everything (see Restarting Phabricator) after upgrading? I can't reproduce this and it looks like the kind of thing that could happen if Phabricator was not fully restarted.

We now send HTML mail by default.