Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make cancelled appeals more obvious in appeal search #13654

Closed
4 tasks
yoomlam opened this issue Mar 10, 2020 · 6 comments · Fixed by #13940
Closed
4 tasks

Make cancelled appeals more obvious in appeal search #13654

yoomlam opened this issue Mar 10, 2020 · 6 comments · Fixed by #13940
Assignees
Labels
Feature: case-details Feature: caseflow-search /search decision reviews Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-queue Source: Bat Team Team: Echo 🐬 Type: design 💅 Used by the design team to keep track of design work that may need design review before shipping

Comments

@yoomlam
Copy link
Contributor

yoomlam commented Mar 10, 2020

Description

UI problem

At the Board's request, two appeals were modified so that the users will not be able to see or search for them based on the docket number.
(The original request from Martina was to delete them so that users are not confused about cancelled appeals and their assignment to users -- screenshots in slack)

  • Martina: "This makes it appear its still active and assigned to a user to work"

Cancelled appeals should be made more obvious in the UI.

Needs Product, Designer, and end-user input.

Per end-user: Show the appeal in search, but show the status as "Cancelled"

Acceptance criteria

  • Distinguish cancelled appeals in the Case Search Results page
    • Do not display “assigned to” and indicate that appeal is cancelled/remove/what have you
    • Display appeals with no issues associated as "cancelled" in the status column of the search page
  • Appeal is still clickable to be able to view the Case Details page

Background/context/resources

Technical notes

Design

Search Cases_Cancelled Appeals Mockup

@yoomlam yoomlam added Feature: case-details Feature: caseflow-search /search decision reviews Priority: Low Reported issue, not a blocker. "Last in" priority for new work. labels Mar 10, 2020
@araposo-tistatech araposo-tistatech added Team: Echo 🐬 Type: design 💅 Used by the design team to keep track of design work that may need design review before shipping Source: Bat Team Product: caseflow-queue labels Mar 10, 2020
@lomky
Copy link
Contributor

lomky commented Mar 13, 2020

what is this chart?

1 | 
2 | |||
3 | ||||||||||
5 | 
8 | 

This is specifically about how appeals appear in the search results page. Later we may want to add something to the Case Details page. Backend change to provide the info that the appeal is changed, but this is mostly front end work

Estimated at a 3.

Backend and frontend changes, with a mild amount of unknown in the AC waiting for final design.

@yoomlam
Copy link
Contributor Author

yoomlam commented Mar 16, 2020

Ultimately deleted the two appeals due to reporting errors.

@pkarman
Copy link
Contributor

pkarman commented Mar 18, 2020

I highly recommend leveraging the appeal.status method to determine the business logic for this, as it is aligned with what BVA users will expect in their reporting.

@hschallhorn hschallhorn added Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. and removed Priority: Low Reported issue, not a blocker. "Last in" priority for new work. labels Mar 18, 2020
@hschallhorn
Copy link
Contributor

Yep, looks like we just don't serialize ama appeals' status, so that value doesn't exist on the front end. That may be the only change we need to add for the status portion of this.

@geronimoramos
Copy link

Making the Canceled status in red #e31c3d makes a lot of sense to make it obvious for the user.

And just a thought, do we want it to be more obvious as well to the user from the Case Details page? Not sure if it's a problem, but an idea would be using a Warning Status alert component at the top.

@pkarman
Copy link
Contributor

pkarman commented Mar 18, 2020

On case details it seemed important to BVA folks to "unassign" the case if it is cancelled, so whatever logic is setting the "assigned to" value should take the status into account.

@hschallhorn hschallhorn changed the title Make cancelled appeals more obvious in the UI Make cancelled appeals more obvious in appeal search Mar 19, 2020
@sahalliburton sahalliburton self-assigned this Mar 31, 2020
@hschallhorn hschallhorn self-assigned this Apr 9, 2020
va-bot pushed a commit that referenced this issue Apr 10, 2020
Resolves #13654

### Description
Pass ama appeal status to the front end to be shown in case search. Do not show appeal assignee if it is cancelled. Color status red for cancelled appeals.

### Acceptance Criteria
- [x] No assignee is shown for cancelled appeals in case search
- [x] Cancelled appeals show a red status of cancelled appeals in case search

### Testing Plan
1. Navigate to http://localhost:3000/search?veteran_ids=377
1. Cancel the appeal
```ruby
Appeal.find_by(uuid: "a7654f2e-3aa1-4efa-b671-ce642d43e455").tasks.each(&:cancelled!)
```
1. Ensure these is no assignee listed
1. Ensure the case status is "cancelled" and red

### User Facing Changes

Before|After
---|---
![Screen Shot 2020-04-09 at 12 46 58 PM](https://user-images.githubusercontent.com/45575454/78919832-7e24a000-7a60-11ea-8257-fbab02ca2fa9.png)|![Screen Shot 2020-04-09 at 12 45 53 PM](https://user-images.githubusercontent.com/45575454/78919845-811f9080-7a60-11ea-9b4b-9d1eaffa85c4.png)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: case-details Feature: caseflow-search /search decision reviews Priority: Medium Blocking issue w/workaround, or "second in" priority for new work. Product: caseflow-queue Source: Bat Team Team: Echo 🐬 Type: design 💅 Used by the design team to keep track of design work that may need design review before shipping
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants