SeanC/APPEALS-40669 | Creation of ‘Pending admin review’ section on Edit Issues Page

[seancva]

Resolves Creation of ‘Pending admin review’ section on Edit Issues Page

Description

Created a 'Pending admin review' section on the edit issues page, if there are pending issue modification requests on the appeal.

Acceptance Criteria

• [ ] Code compiles correctly
• [ ] On the edit issues page, under the 'Requested Issues' section, there is a 'Pending admin review' section
• [ ] Requests are separated based on type:
  • [ ] Request modification section name: Requested Changes
    • [ ] Details included: ‘New issue’ information, Reason for requested modification, Requested by, ‘Original Issue’ information
  • [ ] Request additional issue section name: Requested Additional Issues
    • [ ] Details included: ‘New issue’ information, Reason for requested issue addition, Requested by
  • [ ] Request removal section name: Requested Issue Removal
    • [ ] Details included: ‘Original issue’ information, Reason for requested removal of issue, Requested by
  • [ ] Request withdrawal section name: Requested Issue Withdrawal
    • [ ] Details included: ‘Original issue’ information, Reason for requested removal of issue, Requested by

Testing Plan

1. Login in as one of the VHA users (EX. VHAADMIN)
2. Click "Your Queue"
3. From the "Switch views" dropdown, select "VHA Decision Review Queue"
4. On the 'in progress' tab, click any of the cases
5. On the case details page, click the "Edit Issues" button
6. Verify that the 'Pending admin review' section, is on the page and below the 'Requested issues' section
7. Verify that the Requests are separated based on type
8. Verify the Additional Issues section
9. Verify the Modification section
10. Verify the Removal section
11. Verify the Withdrawal section

Frontend

User Facing Changes

• [ ] Screenshots of UI changes added to PR & Original Issue

BEFORE	AFTER

Storybook Story

For Frontend (Presentation) Components

• [ ] Add a Storybook file alongside the component file (e.g. create MyComponent.stories.js alongside MyComponent.jsx)
• [ ] Give it a title that reflects the component's location within the overall Caseflow hierarchy
• [ ] Write a separate story (within the same file) for each discrete variation of the component

Tests

Test Coverage

Did you include any test coverage for your code? Check below:

• [ ] RSpec
• [ ] Jest
• [ ] Other

Code Climate

Your code does not add any new code climate offenses? If so why?

• [x] No new code climate issues added

[codeclimate[bot]]

Code Climate has analyzed commit 3a3a8dd8 and detected 0 issues on this pull request.

View more on Code Climate.