Design Life-Cycle of a Jira Issue
This checklist covers the steps to follow when designing for an ongoing project. The checklist for starting out to a new design project can be found in the design category.
Understanding the briefing is a crucial step. You can always disucss the details with the team for better understanding the issue.
Estimations are hard, that is why they are called estimations. You'll get better at it over time.
We use Abstract for version controlling and design handoffs. Create a branch named with the jira issue id (e.g. CHECK-54/Add-New-Category).
It is always a good idea to brainstorm with the other designers on the team.
You should follow the UI Style Guide of the project and make sure the new contributions are compatible with the rest of the design.
Design review is a crucial part of our design workflow. Every design should be reviewed and approved by the other designers on the team, so after the last commit you should add other designers as reviewers(on Abstract).
Inform the design team about the task you have worked on, give them contexts so that every designer on the team can be on the same page.
Don't forget to apply the changes from design review if there was any.
We use collections feature of Abstract, you should create a new collection named with the Jira issue #id-number and add related artboards to it.
Also please provide the Abstract collection link of the design.