Non-sequential task identifiers

Weird request… sequential ids stress me out. Tickles my OCD in all the wrong ways. What task is so important it deserves to be #1?

So I’ve written a feature to optionally encode task identifiers as ‘random’ strings using Sqids (formerly HashIds). I’ll push it to a fork when my Gitea account gets approved.

For example, instead of #123 or PROJ-123, the task identifer would be #ZYDC or PROJ-ZYDC

Huh I guess that’s a valid reason for a change.

I’ve just enabled your account. Looking forward to the PR!