Use sequential numbers for support task references #2861
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gunndabad
changed the title
gunndabad
force-pushed
the
support-task-reference
branch
from
1f768cb to
e52f705
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We're moving towards sequential task references so that blocks of tasks can be allocated to an agent more easily. It also removes the chance of collisions that we have with the current random reference generator.
This amends the reference generation to use a sequence. Subsequent PRs will expose this reference on the UI and make it searchable etc.
As part of this I've moved support task creation onto
SupportTaskServiceand amended it to use the new style events. An event handler is added to also create a legacy event since the Change History UI is still working off the legacy events (and we haven't migrated all the legacy events yet).https://trello.com/c/VsWkptwe