Closed lowellrex closed 4 years ago
Hey @joeyyang @rkreyhsig, for the next few sprints I am going to attach tickets to the priorities that we lay out in sprint planning so we have a single reference point for which tickets we should focus on. We probably won't finish all of these tickets, but I think it could be a helpful way to guide the work we do during this two week period. Let's see how this works for us, and let me know when y'all think of ways to make this more useful. Also, I will continue to keep the waffle board up to date if that fits your personal taste more.
@joeyyang @rkreyhsig, below are tickets related to this sprint's higher-level priorities.
@joeyyang @rkreyhsig @tomas-nava, below are tickets related to this sprint's higher-level priorities.
@joeyyang @rkreyhsig @tomas-nava, below are tickets related to this sprint's higher-level priorities.
Task.mark_as_complete!
method@joeyyang @rkreyhsig @tomas-nava, below are tickets related to this sprint's higher-level priorities.
Task.mark_as_complete!
method@joeyyang @rkreyhsig @tomas-nava, below are tickets related to this sprint's higher-level priorities.
@joeyyang @tomas-nava, below are tickets related to this sprint's higher-level priorities.
@joeyyang @tomas-nava, below are tickets related to this sprint's higher-level priorities.
@joeyyang @tomas-nava @annekainicUSDS @youngfreezy, below are tickets related to this sprint's higher-level priorities.
@kevmo, below are tickets that you and I will be working on related to this sprint's higher-level priorities.
@kevmo @lomky, below are tickets that we will be working on related to this sprint's higher-level priorities.
@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint's higher-level priorities.
@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets.
ColocatedTask
s to TimedHoldTask
s #9207@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets. This workload assumes that the Echo team will be able to dedicate 5 developer weeks of time this sprint.
@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets. This workload assumes that the Echo team will be able to dedicate 7 developer weeks of time this sprint.
TaskTable
to use API requests to paginate, filter, and sort tasks #11054@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets.
@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets.
Stayed appeal
admin action task for AMA and Legacy appeals #11278@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets.
@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets.
@kevmo @lomky @hschallhorn, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets.
@kevmo @lomky @lowellrex, below are tickets that we will be working on related to this sprint. We will be using Zenhub to track progress on tickets.
@kevmo @lomky @lowellrex @yoomlam, sprint priorities for this sprint!
@hschallhorn @lomky @lowellrex @yoomlam, sprint priorities for this sprint!
⭐️ 1. ✅ Administratively acting on behalf of other users #11991
⭐️ 1. ✅ Create UI for marking users inactive #12212 ⭐️ 2. ✅ Handle tasks assigned to users that become inactive or are removed from organizations #11811 ⭐️ 3. ✅ Remove inactive users from organizations with automatic assignment of tasks #12303 [late add]
@hschallhorn @lomky @lowellrex @yoomlam, sprint priorities for this sprint! Reduced capacity due to Caseflow Offsite in week 1.
⭐️ 1. ✅ Update the task reassign function #12365
⭐️ 1. ✅ Extend the organizations_user with judge & attorney roles #12420
⭐️ 2. ✅ Create method to reassign all open tasks for a given user #12394
⭐️ 3. (YOOM) Create JudgeTeamRole
objects in application #12481
⭐️ 4. (Blocked by #12481) Backfill data where JudgeTeamRoles should exist #12421
⭐️ 5. (KAT) Update Code using JudgeTeam Admin to Determine Judge / Attorney #12422
@hschallhorn @lomky @lowellrex @yoomlam @ajspotts @jimruggiero sprint priorities for this sprint!
@hschallhorn @lomky @lowellrex @yoomlam @ajspotts @jimruggiero sprint priorities for this sprint!
⭐️ 1. (KAT) Update Code using JudgeTeam Admin to Determine Judge / Attorney #12422
⭐️ 1. (ALEC) Table sort functionality not accessible to keyboard-only or other AT users. Sort buttons should be included in the tab order and be operable by keyboard #12126
⭐️ 1. (HUNTER) Add instructions to reassigned tasks of inactive users #12506
@hschallhorn @lomky @yoomlam @ajspotts @jimruggiero priorities for this sprint!
@yoomlam, @ajspotts, @kevmo, @lomky, @jimruggiero , and @hschallhorn, Here are the sprint priorities for this sprint!
🐬 indicates complete, approved, and waiting for merge after code freeze ends
@yoomlam, @ajspotts, @kevmo, @lomky, @jimruggiero , and @hschallhorn, here are the priorities for this sprint!
Echo engineering team's objective is to enable all teams to track and act on appeals as they move through the board. To that end we have four major lines of effort:
The broader Caseflow team is tracking the roadmap and timelines on a shared mural and using a waffle board to track various tickets that need to be completed.
In July, the Echo team adopted a strategy of voting for determining the level-of-effort estimate for each ticket. A dedicated Github ticket details this initiative in more detail.
1. Single appeal view
This initiative encompasses all of the work that will be done on the case details page. It includes case timeline and the various case details refinements.
2. Collection of appeals views
This includes case search as well as the many different incarnations of the queue table views (judges, attorneys, colocated, generic, all cases view).
3. Task tree
This is somewhat of a catch-all for the plumbing needed to make the task model work: organizational membership, task actions improvements, and maturing/extension of the task model.
4. Pilots
Currently we are piloting the queue functionality with the co-located administrative support team, Board judges, VSOs, and the quality review team. Upcoming pilots include Mail, litigation support, FOIA, and AOD.