# How to handle bugs with Shape Up approach

**URL:** <https://discourse.learnshapeup.com/t/how-to-handle-bugs-with-shape-up-approach/775>\
**Category:** Uncategorized\
**Created:** [April 17, 2021, 9:43am UTC](https://discourse.learnshapeup.com/t/how-to-handle-bugs-with-shape-up-approach/775 "2021-04-17T09:43:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![olek](https://avatars.discourse-cdn.com/v4/letter/o/b2d939/32.png) [@olek](https://discourse.learnshapeup.com/u/olek)\
**Post date:** [April 17, 2021, 9:43am UTC](https://discourse.learnshapeup.com/t/how-to-handle-bugs-with-shape-up-approach/775/1 "2021-04-17T09:43:36Z")

</div>

Hi Guys,

what’s the approach of Shape Up to handle bugs while working on project in 6 weeks cycle?

---

<div class="post-metadata">

**Author:** ![Salmiak](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.learnshapeup.com/salmiak/32/343_2.png) [@Salmiak](https://discourse.learnshapeup.com/u/Salmiak)\
**Post date:** [April 18, 2021, 8:03pm UTC](https://discourse.learnshapeup.com/t/how-to-handle-bugs-with-shape-up-approach/775/2 "2021-04-18T20:03:53Z")

</div>

During the cycle we have an off-cycle team that handles a few different things that are not related to development projects. Bugs is one of those things. But this isn’t really enough to keep up with the bugs we want to address.

So we have added a week at the end of the cool down dedicated at bugs. Going into that week we have groomed a list of bugs that are prioritized _high_ and _medium_. Devs are free to pick from high until there are no high prio bugs left. There’s no priority within these groups. Then the whole team hammers away with daily releases Mon-Thursday.

As this is the last week of the cycle, Friday is dedicated for a hackathon where everyone can do what ever they like.This helps to clear our minds before heading into the next cycle the week after.

We’ve done this for a few cycles now and it seems to fit our company perfectly.

---

<div class="post-metadata">

**Author:** ![olek](https://avatars.discourse-cdn.com/v4/letter/o/b2d939/32.png) [@olek](https://discourse.learnshapeup.com/u/olek)\
**Post date:** [April 19, 2021, 9:30pm UTC](https://discourse.learnshapeup.com/t/how-to-handle-bugs-with-shape-up-approach/775/3 "2021-04-19T21:30:06Z")

</div>

Thanks @Salmiak for your help!

How do you describe, track and manage bugs in Basecamp tool? What are the tips and tricks to organize bugs in Basecamp?

---

<div class="post-metadata">

**Author:** ![Salmiak](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.learnshapeup.com/salmiak/32/343_2.png) [@Salmiak](https://discourse.learnshapeup.com/u/Salmiak)\
**Post date:** [April 20, 2021, 4:08am UTC](https://discourse.learnshapeup.com/t/how-to-handle-bugs-with-shape-up-approach/775/4 "2021-04-20T04:08:39Z")

</div>

We don’t use Basecamp. Instead we use Jira to track bugs. We’ve tried Basecamp but it didn’t really work that well for us. We currently run the cycle projects in ClickUp, but we’re still figuring out how to do that in a good way.

---

<div class="post-metadata">

**Author:** ![olek](https://avatars.discourse-cdn.com/v4/letter/o/b2d939/32.png) [@olek](https://discourse.learnshapeup.com/u/olek)\
**Post date:** [April 26, 2021, 10:54am UTC](https://discourse.learnshapeup.com/t/how-to-handle-bugs-with-shape-up-approach/775/5 "2021-04-26T10:54:16Z")

</div>

Thanks!

My idea is to have one place to track everything. That’s why we have been using Basecamp.

Right now, we have a seperate TODO list for bugs. I thought, maybe there is more efficent way to do that in Basecamp.