Hey thanks for the Office Hours video on QA. Quick question, how do you get images/logos on project folders like Gabriel has in this demo? 5:15 I may have missed this in the stacks/folder functionality, but it looks cool so would like to implement this on my own Home Screen. Gabriel’s Home Screen looks super clean, awesome 🔥
Glad you found it! There is more info on organizing your Home Screen and using Stacks here: 3.basecamp-help.com/article/838-customize-your-home-screen. Thanks for watching! -Kimberly
Hey, great video. 31:24 Gabriel mentioned urgent bugs (reported most likely through support) are handled somewhere else, I assume its handled on-call. Just wondering, how is QA involved in that process,more specifically how are bugs triaged and tested then.
Hey there! You're correct. Urgent bugs are posted in a Card Table in a separate On Call project, usually by the support team. Our QA team you saw in the video watch for incoming bugs, provide additional context for the team where they can (for instance, is this issue likely from a recent feature push?), and share additional steps to reproduce bugs when the path isn't 100% clear. The developers that are on call might tag QA in the comments if they need a second set of eyes on something. Other times, the fix is immediate, scoped and does not require QA to do anything. Hope that helps! - Kimberly (with an assist from Gabriel)
@37signals awesome, thats what I assumed it would be like. I believe the support could also chime in with some simpler QA anyway. Thanks a bunch, Gabriel and Kimberly 🙏. We're trying to build a similar setup in our company and these office hours videos have been really helpful. Keep 'em coming.
@@37signals it would be cool to see how Brian uses Basecamp, how everything contributes to building product strategy and ultimately a pitch. On one of the older videos, I saw how customer support interviews made it to the Product Strategy board. Similar kinda story for features that didn't make it into the cycle. They were put up for consideration in product strategy (I think). I found this process really fascinating since everything just came about into making a product strategy. Would love to see essentially an expansion of this and also how other teams contribute to the strategy as well.
Quick question: Why does your Basecamp look different from ours? We don’t have team projects or the nice HQ icon in the HQ project. Am I missing something?
You're not missing anything! Those "team" and "HQ" labels existed in a previous version and still exist for accounts that started projects when those labels were around. Those projects are just regular projects... nothing special or different about them. Hope that helps! -Kimberly
Hey thanks for the Office Hours video on QA. Quick question, how do you get images/logos on project folders like Gabriel has in this demo? 5:15 I may have missed this in the stacks/folder functionality, but it looks cool so would like to implement this on my own Home Screen. Gabriel’s Home Screen looks super clean, awesome 🔥
Never mind guys….ignore me I have found the option for existing stacks! 😂 Nice one!
Glad you found it! There is more info on organizing your Home Screen and using Stacks here: 3.basecamp-help.com/article/838-customize-your-home-screen. Thanks for watching! -Kimberly
Hey, great video. 31:24 Gabriel mentioned urgent bugs (reported most likely through support) are handled somewhere else, I assume its handled on-call. Just wondering, how is QA involved in that process,more specifically how are bugs triaged and tested then.
Hey there! You're correct. Urgent bugs are posted in a Card Table in a separate On Call project, usually by the support team. Our QA team you saw in the video watch for incoming bugs, provide additional context for the team where they can (for instance, is this issue likely from a recent feature push?), and share additional steps to reproduce bugs when the path isn't 100% clear. The developers that are on call might tag QA in the comments if they need a second set of eyes on something. Other times, the fix is immediate, scoped and does not require QA to do anything. Hope that helps! - Kimberly (with an assist from Gabriel)
@37signals awesome, thats what I assumed it would be like. I believe the support could also chime in with some simpler QA anyway. Thanks a bunch, Gabriel and Kimberly 🙏. We're trying to build a similar setup in our company and these office hours videos have been really helpful. Keep 'em coming.
Love to hear it! Let us know if there's a specific subject you'd like us to cover and we'll consider it. -Kimberly
@@37signals it would be cool to see how Brian uses Basecamp, how everything contributes to building product strategy and ultimately a pitch. On one of the older videos, I saw how customer support interviews made it to the Product Strategy board. Similar kinda story for features that didn't make it into the cycle. They were put up for consideration in product strategy (I think). I found this process really fascinating since everything just came about into making a product strategy. Would love to see essentially an expansion of this and also how other teams contribute to the strategy as well.
Quick question: Why does your Basecamp look different from ours? We don’t have team projects or the nice HQ icon in the HQ project. Am I missing something?
You're not missing anything! Those "team" and "HQ" labels existed in a previous version and still exist for accounts that started projects when those labels were around. Those projects are just regular projects... nothing special or different about them. Hope that helps! -Kimberly
@@37signals Thanks explication 🙏
An agent of ours encountered http 404 and the other one updated her email and then got locked out.
How can we get it fixed?
Thanks
Is this an issues with Basecamp? If so, please email our support team - support@basecamp.com.