I find the google spreadsheet super easy to use and available and accessible for everyone

We are creating a google spreadsheet with all the issues we found. Each issue gets few columns to be filled:

• Area in the product - our features are usually affecting few places in the product, sometimes these places are owned by different developers so this arrangement is more effective.

• Priority (P1, P2, P3) - very important in order to be able to release without finishing everything

• Description - explaining the issue, current behavior, expected behavior, explaining how to recreate the issue.

• Screenshot of the issue / Video in case it’s a flow that needs to be fixed (we paste links we capture with marker.io / loom)

• Type - Server side / Front end (When its not clear I leave blank for the Dev team to fill)

• Status - Open, In progress, Ready for QA

For the columns of area, priority, type and status I add the predefined values as drop down options so it will be possible to filter the list (all open issues, all issues in server etc)

When all blockers (P1s) and P2s are fixed we usually release and all the leftovers, the P3 we move to JIRA issues.

We find this workflow good and efficient for the whole team. Sometimes few designers are involved in the UX QA process, in this case we also add a column for the name of the designers who reported the issue in case a developer needs a further info.

Hope that helps :)

The link now leads to ״This project was removed". I wonder what happened there...

Uggghhhh. Just updated - can't drag boxes with text. WTF? Update : After moving any element i can't move it again... downgrading.

Is that on purpose?

Undo behaviour is totally f#$%&! Elements that were moved are not getting back to the same location after clicking cmd+z

Is there a way to rollback to previous version?

Same here :( this is really frustrating!

The main problem in the workflow you suggedt is is that webflow doesn't give the CMS solutions.. So after your frontend is ready you still need a developer to complete the project..

Thanks Evan for the detailed response. Can you please explain more about layouts behaviour in android ? I understand that assets needs different sizes for different screen densities but how this affects the layouts (what happens to margins, paddings.. do you use %? does it behave like fluid layouts on web?) Thanks :)