I was thinking that eventually some day the plugins/providers we would build would have a frontend as well as backend bits, and the frontend bits would be able to display additional info that may not be deploystream-normalised data, but provider-specific. There is nothing in this PR that prevents that, but it makes it a little tedious to have to change code in two places for that.

While I was testing Github and sprintly I found it useful to get everything that was coming through, and find additional useful fields that I had not initially considered.

That said, there is nothing wrong with being totally explicit here, but it means I will have to test that github and sprintly still work, which I doubt as I was relying on the fact that some basic fields have typically the same names (title, description, etc...).