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

Implements Backend of Case Movement for Blocked Cases #14957

Conversation

lomky
Copy link
Contributor

@lomky lomky commented Aug 13, 2020

Resolves #14260

Description

Creates the backend logic for moving an appeal from the Case Storage to assigned to a judge, cancelling any Distribution blocking tasks along the way.

Acceptance Criteria

  • Please put this work behind the feature toggle: cm_move_with_blocking_tasks
  • This feature should be accessible to the following user groups: CM Team Members
  • CM team members can cancel "blocking tasks" to advance a case to a VLJ
  • CM team members cannot cancel "Blocking for dispatch only" tasks

Testing Plan

  1. Go to ...

Code Documentation Updates

  • Add or update code comments at the top of the class, module, and/or component.
    • New model
    • Spec shared examples

@lomky lomky self-assigned this Aug 13, 2020
@codeclimate
Copy link

codeclimate bot commented Aug 13, 2020

Code Climate has analyzed commit 831ce2a and detected 1 issue on this pull request.

Here's the issue category breakdown:

Category Count
Bug Risk 1

View more on Code Climate.

Comment on lines +54 to +56
# TODO: this _should_ not cancel after we finish
# https://github.com/department-of-veterans-affairs/caseflow/issues/14057
# Distribution Blocking. Update this test to properly pass then!
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO to be addressed in #14057


def self.label
COPY::CASE_MOVEMENT_TASK_LABEL
end

private

def close_and_create_judge_task
def distribute_to_judge
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

renamed to better reflect the why of what's being done in both cases

Comment on lines +477 to +482
factory :extension_request_mail_task, class: ExtensionRequestMailTask do
parent { create(:root_task, appeal: appeal) }
assigned_to { MailTeam.singleton }
assigned_by { nil }
end

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I needed a MailTask type that should actually block distribution

lomky and others added 4 commits August 13, 2020 10:57
New appeal trait for realistic task tree appeal with blocked distribution due to mail
New seeded appeals, 30 in Evidence Window and 30 with Blocking mail tasks
@lomky lomky changed the base branch from master to kat/14260_backend_cancel_block_tasks_main August 13, 2020 18:44
@lomky
Copy link
Contributor Author

lomky commented Aug 13, 2020

replaced with stacked PR starting at #14964

@lomky lomky closed this Aug 13, 2020
@alisan16 alisan16 deleted the kat/14260_backend_cancel_block_tasks branch February 10, 2021 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Case Movement: Implement Backend Logic For Cancellation of Blocking Tasks
1 participant