Tickets in RT now start as new and keep their state on outgoing correspondence#692
Merged
Tickets in RT now start as new and keep their state on outgoing correspondence#692
Conversation
…going correspondence This PR is intended to smoothen the user experience when working in the RT interface: Before this, RT Tickets started out as "open" and would reset to "open", whenever frab would add correspondence. This made it very hard to keep track of Tickets in need of attention, as each Ticket was 'active' by default, even when no outside correspondence was added. Now each Ticket added by frab will initially be marked "resolved" and can be put into active state by manually adding correspondence from RT or via email. Whenever frab adds outgoing correspondence via bulk mails, it resets the RT Ticket's state to what it found it at, so that open Tickets will stay open while resolved Tickets remain resolved and will only be "re"-opened, whenever speakers reply by email.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR is intended to smoothen the user experience when working in the RT interface:
Before this, RT Tickets started out as "open" and would reset to "open", whenever frab would add correspondence. This made it very hard to keep track of Tickets in need of attention, as each Ticket was 'active' by default, even when no outside correspondence was added.
Now each Ticket added by frab will initially be marked "resolved" and can be put into active state by manually adding correspondence from RT or via email.
Whenever frab adds outgoing correspondence via bulk mails, it resets the RT Ticket's state to what it found it at, so that open Tickets will stay open while resolved Tickets remain resolved and will only be "re"-opened, whenever speakers reply by email.