alphagov/transition — pull request #309 by issyl0 (2014-06-06 11:26:12+00:00)
Title: Enable users to add unresolved mappings

- Add a blurb about unresolved mappings and what the point of them is, when the option is selected.
- Mappings marked unresolved added through here get added, correctly, to the database with a type of unresolved.
- Show unresolved as archives in the mappings table, in muted style. Add a question mark with a hover to explain the unresolved type, but why it is marked as an archive and greyed out.
- Show current status when editing unresolved mappings, like we do for redirects and archives.
- Default the mapping type to unresolved in the `MappingsFromHostPaths` import rake task.

This has the side effect of allowing filtering by unresolved, in so far as it doesn't strip Unresolved from the list of type filters. Stripping it out, both with JS enabled and disabled, so that it could be constrained to a separate story, was quite a bit of effort in the end for not so much gain. It doesn't do the actual filtering, right now, but that's what the separate story is for - adding the number of unresolved mappings, the filtering of unresolved mappings, and showing a percentage of mappings which are unresolved. So that story should be right behind this one in priority.