KG - Service Request Resubmission Epic Queue Push Logic Change #2301
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
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.
https://www.pivotaltracker.com/story/show/156705787
Background:
Currently, when a user is submitting or re-submitting a protocol and that protocol has been flagged to "send to epic", our API logic is to put it into the protocol Epic queue. This causes confusion some times, because the user could have re-submitted a protocol without changing anything on the calendar.
Acceptance Criteria:
For a previously successfully submitted to Epic protocol, only when the protocol contains sub-service-requests (SSRs) with Epic services that are changing from Draft to Submitted should be put into the Epic queue instead.