Some stuff I'm thinking of doing in the short term:

• Add an isUrgent flag to issues. Today, this would just make them red or something, eventually this will page oncall.
• Add a isPinned flag to issues, maybe. I'm imagining pacts may have certain issues that we want to persist, like "List of legal documents", "current overall priorities", etc. Putting issues into a permanently open + pinned state might be a good catch-all for this, and if/when that breaks down we can build specific "Document Support" or "Priority List" features. Not totally sure we need this.
• Add bucketing and filtering options to the "all issues" admin view, since this will be the support queue until we eventually outgrow it and do a Nuance backend.
• Actually implement Mana.

Some other stuff:

• We can use R25 to deploy a PHIxxx remarkup rule here on secure. It wouldn't do fancy hovercard/doorkeeper stuff but could at least auto-link which is probably a big chunk of the value.
• Likewise, I think we can deploy a replacement Txxx rule on admin so Txxx links here by default (since admin does not install Maniphest). Not perfect but should be better than nothing.

Ideas, not sure if they're important:

• Add a description to Member so individuals can list their title / contact info / etc?

Email replies don't actually work since mail gets routed to the web tier (mail.phacililty.com) which can't hit admin. I think I can fix this with a mail route.

Test mail from the console now gets routed/accepted properly but real mail still doesn't. I'm going to write this off as possibly being a route propagation issue for a little bit and see if it fixes itself.

This works now: PHI1

Using @mentions in issue comments hits a policy exception because of the slightly odd way pact policy filtering works.

Inbound mail later bounced. I think the issue is that we have a *.phacility.com MX record, but an admin.phacility.com A record. I can't recite all the wildcard vs nonwildcard DNS rules offhand, but I think the A record is shadowing the MX record, e.g. dig mx admin.phacility.com does not produce the right results. I've added an admin.phacilty.com MX record which might sort things out once it propagates.

Inbound mail seems to be working now.

Two outstanding issues:

• (PHI7) Outbound mail isn't working correctly for non-staff, I think it's getting caught in policy filtering.
• (PHI5) Minor state transition when resolving open issues.