311-data
311-data copied to clipboard
hackforla
Modal Neighborhood Districts
Overview
Design what ND filter would look like if the name is long and takes up two rows. We need to do this because names that are too long break sizing rules
Resources/Instructions
Example: EMP CON: Empowerment Congress (don’t abbreviate) “Arts District Little Tokyo”, “Bel Air-Beverly Crest”, etc
View the research deck for details
Design Iterations
Please move ticket between In Progress and In Review to assist PM team
Iteration 1
Link to notes: REPLACE WITH COMMENT URL
Hand Off Materials
Figma Section Name: Modal Neighborhood Districts #1650
Before Screenshot
After Screenshot (Finalized)
Designer Resources
Iteration Dropdown Copy/Paste
<details><summary>Iteration X</summary>
<p>
</p>
</details>
Instructions for Engineering Hand Off
To Start Engineering Hand Off...
- Ensure all Hand Off Materials are filled in
- Add the "ready for dev lead" label
- Leave a comment saying "This ticket is ready for engineering hand off."
Hi @Joy-Truex -- thank you for making this ticket. You've done a good job of adding role, size, milestone, and project board. During our ticket workshop, we created the label draft to indicate that this ticket is still being created (e.g. more details are being added to the description, etc). I'll give a brief overview of what this ticket needs next to continue:
- When you feel like the ticket description is adequate, you will unassign yourself and add the
ready for design leadlabel, and @annaseulgi will give the ticket a look-over. (ticket remains in New Issue Approval) - When design lead is happy with the ticket, we can remove
ready for design leadand addready for prioritization(ticket remains in New Issue Approval) - Product team will add this ticket to the Prioritized Backlog you (or any other design team member) can assign themselves and move the ticket to In Progress.
I know that's a lot! PM team is working to create a process doc, as well as communicate all this to the teams as best as possible.
I'm also going to add my notes on the ticket description now since it looks ready for feedback.
- Before the first line (
Design what ND filter would look like...), please add a line of markdown text:### Overviewso we know exactly what this ticket entails - Add one more sentence to your overview description that explains why this ticket exists. This helps with ticket prioritization (e.g.
Design what ND filter would look like if the name is long and takes up two rows. We need to do this because names that are too long break sizing rules) - Before the line that says
Example:, add a line of markdown text:### Resources/Instructionsso we know that everything below is information useful to the designer - Replace
View the research deck for detailswithView the [research deck](https://docs.google.com/presentation/d/1NBMnS8_znCnYNDNNQrN2Jh5GQZhZmX56rtHME-EewBY/edit#slide=id.p1) for details
wow i really botched this! thank you so much @ryanfchase , having the steps written out is so helpful for me to reference vs just trying to do it from memory!!
You're good @Joy-Truex thank you for making those changes! This ticket is looking good now.
@annaseulgi I think this is ready for prioritization and assignment. If you're happy with it, remove the draft label and add the ready for prioritization label.
Edit: Clearing assignees until someone is actively working on this ticket, or is actively making edits to the description
@ryanfchase this is ready for handoff - https://www.figma.com/file/eF63O8yIGz2soQ4JJFfyoK/311_Data_UXUI?type=design&node-id=11199%3A1918&mode=design&t=4a78S5jUavJL8FJM-1
FYI @bphan002 and I going to review this, and then create a dev ticket as long as we have everything we need. Most likely this will close since the work is done, thanks @Joy-Truex !
