Skip to main content

Nozbe integration

Integration with Nozbe is based on tasks. Each time a new issue is reported to Bugsee, we create a new task in the Nozbe project you mapped the application to.

Make sure you have at least one project in your Nozbe account to map a Bugsee application to. Every account also has a built-in project for tasks that belong to no project, which appears in the mapping step as "Single Tasks".

info

This integration connects to Nozbe Classic (app.nozbe.com). If your team has moved to the current Nozbe apps, this integration will not see those projects.

Authentication​

Supported authentication methods​

OAuth​

Select "OAuth" authentication type and click "Next". You will be redirected to Nozbe and asked to allow Bugsee access to your account. Approve the request to return to the wizard.

Configuration​

There are no specific configuration steps for Nozbe. Refer to configuration section for description about generic steps.

What is synchronized​

  • Task creation. The issue summary becomes the task name.
  • Description. A Nozbe task has no description field, so the Bugsee description is posted as the first comment on the task instead. If that second step fails, the task still exists but arrives without its description.
  • Comments. Comments added to the Bugsee issue are mirrored onto the task.
  • State and summary. Closing or reopening the Bugsee issue completes or un-completes the Nozbe task, and a renamed issue renames the task. Priority and label changes are not sent to Nozbe.

Descriptions and comments are sent as Markdown — see issue-based recipes if you want to change what gets pushed.

Found an issue, typo, or wrong statement on this page? Report it now →