v1.0.33: Autostaffing and many UX improvements/bugfixes

[marcua]

@thisisdhaas and I have collaborated on Orchestra v1.0.33. Shout out to two hackathons in a row of heads-down time to improve Orchestra. This release has one major feature (autostaffing) and a bunch of UX improvements/bugfixes.

We're trying out GitHub's discussions feature to post a summary of the project.

Major feature: Autostaffing

Prior to this version, Orchestra's StaffBot would reach out to qualified experts alerting when a new task was available. Depending on the time of day an expert was working, they might face challenges picking up new tasks. For example, B12 does most of its customer-facing work during US east coast business hours, and so experts who work in that timezone had an easier time picking up new tasks. With v1.0.33, we've released an AutoStaffing module in Orchestra. Here's an overview

• You can read the technical details for this feature in the docs.
• Experts can now tell Orchestra how many hours of new work they would ideally be assigned each day. They can do this for the current week or the next week under Account settings.
  
• To allow this functionality to be introduced carefully, an administrative user can set an upper limit on an experts' daily hours in Django admin (by editing Worker.max_autostaff_hours_per_day). Experts will only see the hours interface if they have nonzero max_autostaff_hours_per_day (defaults to 0 hours/day).
• When looking to staff a project, StaffBot will automatically assign a task to a certified expert who has time available today. It prioritizes projects by Project.priority and experts by Worker.staffing_priority. It estimates the time a task will take by calling the task's Step.get_assignable_hours function, and considers work the expert has already tracked today, as well as work it has previously assigned the expert.
• If a task can't be automatically staffed, StaffBot falls back to messaging experts, alerting them that work is available for them to pick up if they so choose.
• This feature should be introduced with care. Specifically, we strongly believe that experts should not be penalized for turning down work, whether that happens by not accepting a StaffBot request or by asking for a project to be restaffed if they are automatically assigned to the project and prefer not to work on it.

Bugfixes and UX improvements

• Project management bugfix: you can now add an expert to a project using their Orchestra Worker username rather than having to know their Slack username.
  

• Easier Slack access in dev: we now correctly/consistently use Slack IDs anywhere a Slack message is sent, and enable Slack usage in dev.

• Available tasks now display staffing request creation time (see the Available since column) rather than task creation time. The table is also now sorted by project priority and then by request creation time.
  

• Clicking save on a settings screen now offers visual confirmation of the save.
  

• Notification settings bugfix: You can now save notification preferences again.
  

• Project management bugfix: The 'view in admin' button at the top of a project's management screen works again.