# Color bubbles not showing after import

**URL:** <https://community.vikunja.io/t/color-bubbles-not-showing-after-import/1648>\
**Category:** Bug\
**Created:** [22 September 2023 14:21 UTC](https://community.vikunja.io/t/color-bubbles-not-showing-after-import/1648 "2023-09-22T14:21:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![garlictoast](https://community.vikunja.io/letter_avatar_proxy/v4/letter/g/db5fbb/32.png) [@garlictoast](https://community.vikunja.io/u/garlictoast)\
**Post date:** [22 September 2023 14:21 UTC](https://community.vikunja.io/t/color-bubbles-not-showing-after-import/1648/1 "2023-09-22T14:21:15Z")

</div>

After importing my data to a new instance, the color bubble that indicate the category on the main page are not showing up. This is after trying a database import and after using the built in export/import. I crawled the settings and did not see a setting to enable/disable these.

 ![Screenshot 2023-09-22 092323](https://community.vikunja.io/uploads/default/original/1X/780c00c8d3f3f9738fc994002b402887cf3c21f6.png)

Side note: I think the issue reports in the git repos are broken. I am not able to start a new issue within the repos.

---

<div class="post-metadata">

**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\
**Post date:** [27 September 2023 08:20 UTC](https://community.vikunja.io/t/color-bubbles-not-showing-after-import/1648/2 "2023-09-27T08:20:06Z")

</div>

Did you import via the cli (`vikunja restore` command) or user import via settings?

> [@garlictoast](#):
>
> I am not able to start a new issue within the repos.

What does not work? What’s the error message?

---

<div class="post-metadata">

**Author:** ![garlictoast](https://community.vikunja.io/letter_avatar_proxy/v4/letter/g/db5fbb/32.png) [@garlictoast](https://community.vikunja.io/u/garlictoast)\
**Post date:** [27 September 2023 11:45 UTC](https://community.vikunja.io/t/color-bubbles-not-showing-after-import/1648/3 "2023-09-27T11:45:30Z")

</div>

I was not aware there was a CLI option. I will try that this evening. I have tried through the user settings and a SQL dump/restore.

I think it is also worth noting that I also tried a completely fresh install and the bubbles are not appearing in the tasks list.

Github issues seems to be fixed now. Before, it was just redirecting itself back to the selection page for a new issue.

---

<div class="post-metadata">

**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\
**Post date:** [27 September 2023 15:40 UTC](https://community.vikunja.io/t/color-bubbles-not-showing-after-import/1648/4 "2023-09-27T15:40:20Z")

</div>

> [@garlictoast](#):
>
> I was not aware there was a CLI option. I will try that this evening.

The CLI option will only restore a full dump (`vikunja dump` and `vikunja restore` commands) but the user import is probably what you want in your case.

I will have a look.

Which version are you using?

---

<div class="post-metadata">

**Author:** ![garlictoast](https://community.vikunja.io/letter_avatar_proxy/v4/letter/g/db5fbb/32.png) [@garlictoast](https://community.vikunja.io/u/garlictoast)\
**Post date:** [28 September 2023 00:51 UTC](https://community.vikunja.io/t/color-bubbles-not-showing-after-import/1648/5 "2023-09-28T00:51:24Z")

</div>

Frontend Version: 0.21.0  
API Version: v0.21.0

Old setup was also using 0.21 for API and frontend as well.

---

<div class="post-metadata">

**Author:** ![kolaente](https://community.vikunja.io/user_avatar/community.vikunja.io/kolaente/32/5_2.png) [@kolaente](https://community.vikunja.io/u/kolaente)\
**Post date:** [29 September 2023 18:48 UTC](https://community.vikunja.io/t/color-bubbles-not-showing-after-import/1648/6 "2023-09-29T18:48:04Z")

</div>

Looks like this was a frontend issue. Should be fixed in [66c7a05cdb](https://kolaente.dev/vikunja/frontend/commit/66c7a05cdb03ae728ddc7a6f22954568dea04f89). Please check with the next unstable build to see if the problem went away.
