Delayed issues

## Summary

It would be nice if you could set a timer on when to actually publish an issue, for instance, if you wanted to be reminded about a feature to implement in 2 days you could set an issue to be published 2 days from whenever you submitted it.

Because the code is browser client-driven now, this could be tricky to implement because the extension would need to be active to do the work. @kaufmann42 mentioned we could probably use localstorage to maintain a list of issues and a date to publish them, then just check that list each time the extension becomes active.

Another option would be to host the server with a DB and handle this there. Either way, this would be nice to have!

Start by reviewing the browser client-driven issue creation flow and how the Chrome extension becomes active. Compare the proposed localStorage queue, checked on extension activation, with a server-and-database design; done means users can schedule an issue and have it published at the requested time.

Written by the indexing model from the issue text.