[Northumberland] Fetch 'detailed_information' (extra details) to/from Alloy & assigned user to Alloy

[nephila-nacrea]

For https://mysocietysupport.freshdesk.com/a/tickets/3082 / https://github.com/mysociety/societyworks/issues/4507.

[skip changelog]

[codecov]

Codecov Report

Attention: Patch coverage is 92.00000% with 2 lines in your changes missing coverage. Please review.

Please upload report for BASE (master@40461e5). Learn more about missing BASE report.
Report is 2 commits behind head on master.

Files with missing lines	Patch %	Lines
perllib/FixMyStreet/App/Controller/Report.pm	85.71%	0 Missing and 1 partial ⚠️
perllib/Open311/UpdatesBase.pm	90.90%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff            @@
##             master    #5147   +/-   ##
=========================================
  Coverage          ?   82.51%           
=========================================
  Files             ?      406           
  Lines             ?    31732           
  Branches          ?     5049           
=========================================
  Hits              ?    26185           
  Misses            ?     4056           
  Partials          ?     1491           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dracos]

All clear and makes sense :) A few suggestions, shout if don't make sense

[dracos]

I guess issue here is if someone edits the extra detail, and the assignment, that has two updates rather than combining them in the one. Do we think that matters? I'm not sure. I like the way you've hooked it round planned_reports to catch any usage there, I wonder if there's some way that can be hooked in here.

[nephila-nacrea]

Thanks ^.^ I didn't think it mattered - and trying to consolidate them into one update seemed like it would be a headache, given that the assigned user logic kind of exists in its own bubble.

[nephila-nacrea]

Am still wondering, though, what I should do about the updates displaying on the /report/<id> page :-/

[dracos]

You can see in report/updates.html there's a "IF update.get_extra_metadata triage_report" type thing to skip those updates. Perhaps we take this opportunity to add a staff_only flag to updates (for there as well) and have it use that to skip these updates. Seems easier than trying to decide based on contents (given the updates in the template can include questionnaire replies as well etc).
Not sure that's easy for the update on detailed information, though, hmm.