6 ms·

Or, you could create a separate issue for designing the project and for implementing it. Then cc the PM on both. Done! At the end of the day, someone should be

by kwiens 10y ago

Or, you could create a separate issue for designing the project and for implementing it. Then cc the PM on both. Done! At the end of the day, someone should be responsible for completing the issue. Is it a PM? Assign it to them. Is it a designer? Assign it to them. We use Codetree as well, and it's wonderful. But the key is to use small, focused issues with a single individual accountable for each one.

awaxman11 10y ago
We do create separate issues for design and development :) IMO having an explicit assignee is more clear than cc'ing someone, and it also makes it easier to see all issues that you're currently responsible for moving forward. At the end of the day whatever works best for the given team is what should be used. I don't think there is a definitively right or wrong approach. Our current approach works quite well, and this new feature is going to make things even easier.