Ticket scheduling enhancements #878
Merged
Conversation
This file contains 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
Collaborator
wrongecho
commented
Feb 12, 2024
wrongecho
commented
- Prevent scheduling dates in the past (also for API keys expiry date)
- Correct the ticket URL in the agent email
- Update the onsite value in the database when scheduling a ticket
- Reword the internal note to include a user friendly time and whether the ticket is onsite/remote
- Prevent scheduling dates in the past (also for API keys expiry date) - Correct the ticket URL in the agent email - Update the onsite value in the database when scheduling a ticket - Reword the internal note to include a user friendly time and whether the ticket is onsite/remote
|
Test these changes at: https://scheduling878.pr-review.itflow.org |
|
|
nice work! @wrongecho |
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.