KG - Remove "Get a Cost Estimate" Button / Default Status #2278
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
kayla-glick
force-pushed
the
kg-remove_get_a_cost_estimate
branch
from
3f3e6ea
to
ca521c2
Compare
Stuart-Johnson
approved these changes
Apr 15, 2020
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/168670315
Background:
The "Get Cost Estimate" functionality has been causing user confusions, and some times impeding service provider's workflow.
Acceptance Criteria:
1). Remove "Get Cost Estimate" button from SPARCRequest pages;
2). Take "Get Cost Estimate" away from the default statuses for SPARCCatalog;
3). "Get Cost Estimate" status should behave like an admin status from now on. It should show up in the status list from SPARCDashboard Admin Edit section, but not available to study team users.
4). It should behave as an updatable status, which means that it will be updated to submit when user re-submit the request.
5). Migrate historical data (If ever submitted before, move it to submitted; otherwise move to draft)