Closing as Ponder no longer has voting

A custom panel might be a good solution. Our primary concern is the lack of discover-ability of (a) the ability to link Jira bugs with Differentials and (b) the mechanism to link a jira account with the phabricator account

In our instance the LB handles SSL but we already account for that in preamble.php

okay - I'll just fix this

I suspect its a mixture of history and expectations since Phabricator is used solely as a review system and not as a primary communication mechanism.

I agree. This feature is suboptimal from a complexity and product point of view. Personally, I'd love to see much more powerful Herald system than specific features added to solve smaller use cases. I wasn't trying to ask you to implement this feature so much as I was trying to say that the underlying problem is real and ought to be solved.

That would be helpful and solve the entire problem if emails were completed post-transaction (i.e., one didn't get an email for being a reviewer and then another for being removed). I'd love to add a Herald rule that says 'if any of these projects are added, remove them'.

@epriestley The FreeBSD install is seeing a lot of confusion around this. We have some groups used for policy ("all committers", "all people with access to this repo") which are getting added to reviews. This causes the main dashboard to be useless and likely causes people to filter from phabricator.

One use case I'd like for you to consider is that the build logic might want to insert data into the commit log or differential revision. For example we may want to add reviewers, subscribers, Jira tickets (from the branch name), etc. While some of this case is handled by Herald, not all of it can be without re implementing existing logic in custom PHP

right, I wasn't sure if it was a special case of either of those, but I figured I'd ask just in case.

Yes it would. I might be more explicit and say which state it actually is in.