-
Notifications
You must be signed in to change notification settings - Fork 19
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Display completed ChangeHearingRequestTypeTask info on timeline (#15395)
Resolves #15193 ### Description - return `timeline_title`, `converted_at`, and `converted_by` from `TaskSerializer` - modify component `TaskRows` to include logic for displaying the relevant fields for `ChangeHearingRequstTypeTask` - write storybook component for `TaskRows` - refactor `Tasks.js` - write a feature test in `spec/feature/hearings/convert_travel_board_hearing/edit_hearsched_spec.rb` - bunch of refactors in legacy_appeal and appeal ### Testing Plan #### Dev 1. Find a travel board appeal and visit the case details page `http://localhost:3000/queue/appeals/VACOLS_ID` the following should find any vacols cases that are travel board and build them (ported from `FetchHearingLocationsForVeteransJob` ``` VACOLS::Case .where( # Travle Board Hearing Request bfhr: VACOLS::Case::HEARING_PREFERENCE_TYPES_V2[:TRAVEL_BOARD][:vacols_value], # Current Location bfcurloc: LegacyAppeal::LOCATION_CODES[:schedule_hearing], # Video Hearing Request Indicator bfdocind: nil, # Datetime of Decision bfddec: nil ) .map do |vacols_case| AppealRepository.build_appeal(vacols_case, true) end ``` if that does not work, you can update the fields (`bfhr: VACOLS::Case::HEARING_PREFERENCE_TYPES_V2[:TRAVEL_BOARD][:vacols_value]`, `bfcurloc: LegacyAppeal::LOCATION_CODES[:schedule_hearing]`, `1bfdocind: nil`, `bfddec: nil`) in `Generators::Vacols::Case` and create a travel board vacols case ``` v = Generators::Vacols::Case.create(attrs: Generators::Vacols::Case.case_attrs) a = AppealRepository.build_appeal(v, true) ``` 2. Complete the change hearing request type task 3. Scroll down to Case Timeline and see that the completed task displays as intended #### Storybook 1. Go to storybook 2. look at `queue/CaseTimeline` ### User Facing Changes - [x] Screenshots of UI changes added to PR & Original Issue BEFORE|AFTER ---|--- <img width="605" alt="Screen Shot 2020-10-07 at 2 16 48 PM" src="https://user-images.githubusercontent.com/20735998/95371223-e33e3e80-08a7-11eb-9707-cca518fd5831.png">|<img width="601" alt="Screen Shot 2020-10-07 at 2 17 29 PM" src="https://user-images.githubusercontent.com/20735998/95371185-d91c4000-08a7-11eb-9bc3-c09461c5edbc.png"> ### Storybook Story *For Frontend (Presentationa) Components* * [x] Add a [Storybook](https://github.com/department-of-veterans-affairs/caseflow/wiki/Documenting-React-Components-with-Storybook) file alongside the component file (e.g. create `MyComponent.stories.js` alongside `MyComponent.jsx`) * [x] Give it a title that reflects the component's location within the overall Caseflow hierarchy * [x] Write a separate story (within the same file) for each discrete variation of the component
- Loading branch information
Rubaiyat Rashid
authored
Oct 14, 2020
1 parent
9251ed5
commit 0324c07
Showing
26 changed files
with
436 additions
and
166 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
Oops, something went wrong.