Open gabydisarli opened 1 month ago
Revisit the timing of this in Refinement, per New triage meeting.
@PaulKuykendall I’ve removed the AC. “DEV tickets have been created and linked.” For these larger features, the development team will decide how they want to handle the tickets.
Historically, for smaller updates, the designer would create the dev ticket because it was a straightforward 1:1 arrangement. For these larger Org model features, the development team will likely break up the work into multiple tickets.
Therefore, it makes more sense for them to write their tickets. In the Feature Kickoff section, I’ve noted that we’ll discuss ticket creation with the dev team during that time. We’ll work closely with them to help create the tickets, but we won’t be creating the tickets ourselves.
Issue description
We have a lot of filtering needs across the different tables in the Org model pages. We've designed some basic filtering so far, which is great for our non-org users. But we need to design a more robust filtering solution to meet this need. We're creating a ticket to design something that works for all the pages, instead of just the initial flows we've focuses on (domains, domain groups).
Acceptance criteria
Additional context
The steps below are a general checklist of the process to follow after designs have been created and are ready to share.
Phase 1: Team Review (#2455)
Phase 2: Feature Kickoff
Links to other issues
🔄 Relates to: #2440