We are updating our ticket creation process for Designers on the DST. We currently have 2 GitHub templates that are used for Design work and we believe that these generalized templates could have more specificity for the different task that Designers do. Some ticket templates could be:
[ ] Discovery/Research
[ ] Doc site updates/Documentation
[ ] New component/Updating a component
[ ] Pt.2 of new components or updates (ex. publishing changes/examples)
[ ] Adding a tokens or icons
Note: One thing to make sure we emphasize in the new tickets is making the Designer to Engineer process more formal to make sure that handoff is happening for each design ticket.
[ ] Figure out how we want to rework the github ticket templates.
[ ] Think about if there are any other ways to make the ticketing process easier for Designers (Reach out to the other DST designers for advice or ideas)
[ ] Update the current templates and merge the current templates into one template (Do we need to look at Engineering tickets as well to bridge the design/engineering handoffs?)
[ ] Create the new templates
Acceptance Criteria
[ ] Review with DST Designers
[ ] Review with DST PO/PM's
[ ] The current issue template for Designers is updated and any new issue template have been created
[ ] Any other updates to the GitHub process have been created or ticketed
Description
We are updating our ticket creation process for Designers on the DST. We currently have 2 GitHub templates that are used for Design work and we believe that these generalized templates could have more specificity for the different task that Designers do. Some ticket templates could be:
Note: One thing to make sure we emphasize in the new tickets is making the Designer to Engineer process more formal to make sure that handoff is happening for each design ticket.
Details
Tasks
Acceptance Criteria