Add user-readable Ticket ID field about govflow HOT 3 CLOSED

@amirozer sounds good.

1. We can also create a data migration that backfills these IDs for existing requests.
2. I like the format for the default ID based on date and increment
3. Regarding your point 3, I'm less sure about the use case for allowing an external system to set these IDs in order to continue updating a ticket based on an existing ID from another system. We can't guarantee that these external systems issue IDs that are unique per jurisdiction - eg they may be unique per department for all we know. I'm just not sure it is not better to always issue our own ticket ID based on the format you suggest, which we can guarantee is unique in a given jurisdiction context, and then, if we have a real use case, add a field for external identifier(s).

from govflow.

@pwalsh re: 3, I've based this requirement on the fact that we have an immediate need to import external systems' data into the platform. We already do this today with dozens of clients, and we already today import the same tickets multiple times, updating existing tickets, so we do need an external reference ID. I'll check if we have any client that has multiple hotlines integrated. If we do, I suggest the import mechanism will optionally add a prefix to ticket numbers, by import source.

from govflow.

Shipped in #53

from govflow.