dlau
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # Ability to route VHA SCT appeals [Dogfooding](https://deviq.com/practices/dogfooding) is to run through as many relevant user scenarios as possible. Ideally, the individual scenarios work perfectly as intended. The reason it's important that we go through this process is to ensure the feature is ready for production. The purpose of internal testing is to identify potential gaps or defects so that items can be resolved prior to release. ## Capturing deficiencies It's best that we document any issues that we discover in as much of a uniform standard as possible so that upon later review, we're able to parse the individual instances as easily as possible for potential translation to tech debt/tech improvement Jira tickets. </br> Here's the template that we've decided to use for this session. So the goal is to fill it our for each individual discovery as throroughly as possible to capture the maximum amount of information on the particular issue: 1. Description of issue -> 2. Expected result (what **should've** occurred) -> 3. Actual result (what **did** occur) -> 4. Steps to reproduce -> 5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage) -> 5. Relevant screenshot(s) * screenshots are easy to add to hackMD, simply capture the shot you want on your machine, then drag and drop it into the doc! ### 1 1. Description of issue -> Inability to view appeal create in scenario 2, step 4 in judge distribution 2. Expected result (what **should've** occurred) -> judge's assign page loads to distribute/request appeal 3. Actual result (what **did** occur) -> inability to load queue/CSS_ID/assign 4. Steps to reproduce -> login as judge user and attempt to navigate to /queue/CSS_ID/assign 5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage) -> high, disruption to current distribution process 6. Relevant screenshot(s) N/A ### 2 1. Description of issue -> 2. Expected result (what **should've** occurred) -> 3. Actual result (what **did** occur) -> 4. Steps to reproduce -> 5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage) -> 5. Relevant screenshot(s) ### 3 1. Description of issue -> 2. Expected result (what **should've** occurred) -> 3. Actual result (what **did** occur) -> 4. Steps to reproduce -> 5. Severity (**low**: minimal/non-blocking, **medium**: potentially blocking, **high**: significant blocker/work stoppage) -> 5. Relevant screenshot(s) ## Possible fixes needed 1. ## USERS | Tester | User ID | Scenario | Vet ID | Pass/Fail | | -------- | -------- | -------- | -------- | -------- | | Heather | BVA Intake User (CF_KIRK_283) and Judge (TCASEY_JUDGE) | 1-2 | 700032764 | 1-PASS 1, 2-Deficiency reported | | Sean | SCT User (CF_KIRK_283) | 1, 3-8 |N/A | 3-8:PASS | | Al | Attorney(CF_SCOTTY_283) |3-9 | N/A | 9: PASS | | Clay | BVA Intake User (CF_KIRK_397) and Judge | 1-2 | 700060379| 1-PASS; 2-FAIL; 3-PASS; 4-PASS; 5-PASS; 6-PASS; 7-PASS; 8-PASS; 9-PASS | | Jonathan | SCT User (CF_LAFORGE_283) | 1, 3-8| N/A | | | Oluchi | Attorney (CASEFLOW_397) | 3-9 | N/A | | extra User IDs: extra Vet IDs: BVA Intake IDS: CF_KIRK_283, TCASEY_JUDGE (283), CF_MCCOY_317 Judge IDS: CF_HEH_283, TCASEY_JUDGE, CF_MCCOY_317 TCASEY station id: 283 Logins.md: https://github.com/department-of-veterans-affairs/appeals-qa/blob/ed1c6f26b8c96d0f88bf16fd0804d164ce1eea88/TestData/LOGINS.md ## Scenarios ## 1 - User intakes a VHA appeal and confirms the appeal is distributed to the SCT queue 1. Sign in as your assigned BVA Intake user 2. Navigate to https://appeals.cf.uat.ds.va.gov/intake 3. Intake a 10182 with Veterans Health Administration (VHA) as the benefit type and add a VHA issue. Select "NO" for pre-docketing. 4. Submit the appeal to be docketed and take note of the appellant name and Veteran ID **(Clay: Augustus Marso's (ID #700060379 - VHA)** 6. Intake another 10182 with two issues: one VHA issue and the other a non-VHA issue 7. Submit the appeal to be docketed and take note of the appellant name and Veteran ID **(Clay: Augustus Marso's (ID #700060379) - VHA/non-VHA)** **[Pass to internal team SCT user]** 7. Sign in as your assigned SCT user 8. Navigate to 'Assign SCT Appeals team cases' 9. Confirm the appeals are seen in the SCT queue Bulk Assign page 10. Take note of the appellant name and Veteran ID associated with these two appeals ## 2 - User intakes a non-VHA appeal and confirms the appeal is distributed to a judge queue 1. Sign in as your assigned BVA Intake user 2. Navigate to https://appeals.cf.uat.ds.va.gov/intake 3. Intake a 10182 with any benefit type other than Veterans Health Administration (VHA) and add an issue to the appeal 4. Submit the appeal to be docketed 5. Sign in as your assigned Judge user 6. Click the switch views button and select 'Assign [Judge] team cases' to navigate to 'Cases to Assign' page 7. Select 'Request more cases' 8. Confirm the appeal is in the judge's queue ## 3 - SCT user assigns cases to attorney 1. Sign in as your assigned SCT user 2. Navigate to https://appeals.cf.uat.ds.va.gov/queue 3. Click the switch views button and select 'Assign SCT Appeals team cases' to navigate to 'Cases to Assign' page 4. Ensure the 'Assign 0 cases' button is disabled 5. Select the 2 cases intaken in Scenario #1 and ensure the "Assign 2 cases" button is still disabled 6. Select an Attorney from the drop down *(this should be the attorney your group has a login ID for)* 7. Confirm the 'Assign 2 cases' button is now enabled 8. Click the 'Assign 2 cases' button and verify a success banner appears confirming you have successfully assigned the cases to the attorney 9. Navigate to the Completed tab and confirm the two cases are in the Completed tab **[Pass to internal team Attorney user]** 10. Sign in as the Attorney the cases were assigned to 11. Navigate to https://appeals.cf.uat.ds.va.gov/queue 12. Confirm receipt of the two appeals that were assigned to you in the Assigned tab ## 4 - Attorney has a SCT appeal and sends draft decision to judge 1. Sign in as your assigned attorney user 2. Navigate to the case details page for an appeal in your queue *(choose any appeal except for the 2-issue appeal submitted in Scenario #1)* 3. Select the 'Decision ready for review' task action 4. Click on the 'Add Decision' button 5. Select 'Allowed' for the Disposition on the appeal 6. Enter any Description text 7. Press Continue and ensure you are navigated to the "Submit Draft Decision for Review" page 8. Enter '12345-12345678' as the Document ID 9. Press Continue to submit the appeal to the judge (name should already be populated) 10. Confirm you are navigated back to your queue and a banner appears that reads "Thank you for drafting [Appellant's name]'s decision. It's been sent to [Designated Judge] for review. If you made a mistake, please email your judge to resolve the issue." ## 5 - Attorney returns an SCT Appeal back to the SCT team 1. Sign in as your assigned attorney 2. Navigate to https://appeals.cf.uat.ds.va.gov/queue 3. Select the appeal that was assigned to you with two issues 4. Select the 'Cancel task and Return to Specialty Case Team' task action 5. Ensure a modal appears and the 'Return' button is disabled 6. Enter any text in the text field and ensure the "Return" button is now enabled 7. Click 'Return' to return the appeal back to the SCT queue 8. Confirm a banner appears and reads "You have successfully returned [Appellant name] case to the SCT Queue. If you have made a mistake, please email SCT Coordinator to manage any changes." **[Pass to internal SCT user]** 9. Sign in as your assigned SCT user 10. Navigate to https://appeals.cf.uat.ds.va.gov/organizations/specialty-case-team 11. Confirm the appeal returned from the attorney is in the 'Action Required' tab ## 6 - User Assigns a Single Case to an Attorney From the Case Details Page 1. Sign in as your assigned SCT user and navigate to the queue 2. Select the case that was returned by the attorney in the 'Action Required' tab 3. Select the 'Assign to Attorney' task action when on the case details page 4. Click on the "Select or search" dropdown and select an attorney to send the case to *(this should be the attorney your group has a login ID for)* 5. Enter any text into the textbox 6. Click the "Assign task" button 7. Verify a success message appears confirming the case has been sent to an attorney 8. Verify you are redirected to the 'Action Required' tab and the case is in the "Completed" tab of the SCT queue **[Pass to internal Attorney user]** 9. Sign in as the attorney the SCT user assigned the case to 10. Navigate to https://appeals.cf.uat.ds.va.gov/queue to your Assigned tab 11. Confirm the case that was assigned to you by the SCT user is in your Assign tab ## 7 - User splits an Appeal 1. Sign in as your assigned SCT user and Navigate to https://appeals.cf.uat.ds.va.gov/organizations/specialty-case-team 2. Select a staged appeal that has two issues: a VHA and non-VHA issue 3. On the case details page, select "Correct issue" where you will be redirected to the Edit issues page 4. Confirm 'Split Appeal' button is present 5. Select 'Split Appeal' and confirm you are redirected to the 'Create new appeal stream' page 6. Select any reason why the appeal should be split 7. Select the non-VHA issue and click continue. You should be directed to the 'Review and confirm new appeal stream' page 8. Confirm a message appears under the non-VHA issue (appeal stream) thats reads "This appeal stream has no Specialty Case Team issues. Upon split, it will be routed to regular distribution." 9. Click split appeal 10. Confirm page moves back to case details page and banner appears that reads "You have successfully split [Veteran] appeal. This new appeal stream has the same docket number and tasks as the original appeal." 11. Confirm the number of issues has changed from 2 to 1 on the original appeal and only the VHA issue exists ## 8 - SCT user modifies claim to remove VHA issue 1. Sign in as your assigned SCT user, select a staged appeal from the bulk assign page and navigate to the case details page 2. Select 'Correct issues' to be navigated to the Edit issues page 3. Remove the VHA issue and add a non-VHA issue to the appeal 4. Click "Save" on the modal 5. Click "Yes, save" to confirm 6. Click "Move" on the second modal 7. Ensure a confirmation success banner appears 8. Confirm appeal is removed from SCT queue bulk assign page ## 9 - User Edits a non-VHA appeal to be a VHA SCT appeal 1. Sign is as your assigned attorney and select a staged appeal 2. Select 'Correct issues' where you will be navigated to the Edit issues page 3. Add a VHA issue to appeal 4. Confirm the appeal is removed from attorney's queue **[Pass to internal SCT user]** 5. Confirm appeal appears in the SCT queue on the Bulk assign page

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully