![]() ![]() ![]() We should only use Zeplin for layout-referred discussions and Jira for status-related comments.We should separate somehow the sections into smaller sections so that we can differentiate pages and features.We need some kind of link to the files from Jira to Zeplin and back.We should stop to upload everything in Jira and Zeplin and should have one single point of truth instead.Every designer, project manager and UX conceptioner was making his own notes which we clustered together and discussed as a team. (Yeah, ok… we should have known…) Second Approach: Collecting the NeedsĪfter we left a big mess in our tool, we sticked our heads together again and started from scratch. … Until we corrected the first final screen and everybody was confused. So we used a final tag for every screen that was final. But then… ehm… see for yourself:Īlso there have been a lot misunderstandings when a design is ready. For the first 20 tickets it was actually a good idea. ![]() We used tags for the ticket numbers of Zeplin and to differentiate the breakpoints. In the first step we tried to clean up the whole overview with using sections for pages and maintain the layouts with tags. To put 25 links in one ticket doesn’t make sense at all. But what about the status? Informations like deadlines, blockers, priority: These infos should still belong to the the Jira board to ensure the transparency in a jira-working company.Īnd how should you link Jira tickets to Zeplin files and the other way around? We can’t link to sections only to files which is often confusing. As I mentioned before: The comments in zeplin should be the desired channel for feedback in layouts. There is also a complexity in choosing the right communication channel. And we have to care about different breakpoints as well. And we need a possibility to distinguish between pages and their features. We have an output of over 80 changing and new layouts a day. But if you have a very complex ecommerce product this won’t help you at all. Yes, they gave us the feature “ sections” a couple of months ago to combine screens in one area - what makes everything a little bit better. Using the comment feature on the layout for example is way better, then explaining in Jira which button has to change how or which whitespace we need to decrease.īut: the sorting of layouts in zeplin is a mess. Zeplin combines some features which are optimizing our work process, presentations, feedback rounds and is exporting code snippets and assets. We chose Zeplin for working closely with stakeholders, designers, UX conceptioners and frontend developers together. But as a graphic-working team we need other tools to have a better connection between our UX, UI team and the development teams. If you are working with Jira and Zeplin, you should read this!Īt ABOUT YOU we work with Jira through almost all departments. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |