You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I first installed the - very cool - HabitRPG Chrome extension it automatically created a habit for my Asana task-completion. However I then deleted this habit, and it's not reappearing when I disable and reenable Asana integration in the extension's preferences, or even when I uninstall and reinstall the extension. This means I've lost Asana integration forever. How can I fix this, or is this a bug in the extension that needs fixing?
When I first installed the - very cool - HabitRPG Chrome extension it
automatically created a habit for my Asana task-completion. However I then
deleted this habit, and it's not reappearing when I disable and reenable
Asana integration in the extension's preferences, or even when I uninstall
and reinstall the extension. This means I've lost Asana integration
forever. How can I fix this, or is this a bug in the extension that needs
fixing?
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/69
.
Sorry if I was unclear. The 'Asana task in HabitRPG' that I was referring to is a habit called 'todos'. However since uninstalling and reinstalling the extension, this task has automatically been recreated - it appears there was just a lag here. Ideally it'd get recreated after being deleted whenever you disable and reenable Asana integration in the extension's preferences. But you probably have more valuable tasks to work on than that :)
When I first installed the - very cool - HabitRPG Chrome extension it automatically created a habit for my Asana task-completion. However I then deleted this habit, and it's not reappearing when I disable and reenable Asana integration in the extension's preferences, or even when I uninstall and reinstall the extension. This means I've lost Asana integration forever. How can I fix this, or is this a bug in the extension that needs fixing?
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: