Notion Integration

Notion

Notion is a workspace and documentation service. You can use its databases as an issue tracker. LadyBug Tracker uses a Notion database as the project, and each page in it as an issue.

At this time, this integration is in the beta stage.

Authentication

Notion does not use a user name and a password. It uses an internal integration secret. To connect the plugin to Notion, do these steps:

Open https://www.notion.so/my-integrations, then make a new internal integration. In the login window, the Create Integration button opens this page.
Copy the secret of the integration into the Internal Integration Secret field in the login window.
Open the database that you want to use. Then share it with the integration (Share menu > select your integration).

Step 3 is necessary. If you do not share the database with the integration, the API cannot see the database. Notion then reports the database as not found, not as forbidden. Thus a missing share looks like an incorrect database name.

The host address is always https://www.notion.so. The integration secret already applies to only one workspace.

Project setup (Notion service)

Project selects the database by its title.

The user defines the properties of a Notion database. Thus the plugin matches them to its own fields by name and type. If a property is missing, the plugin does not show it as a field. The project verification tells you which properties it did not find. It does not fail. This is the mapping:

Notion property	Type	Plugin field
title property	title	Summary
Description	text	Description
Status	status or select	Status
Priority	select	Priority
Assignee	people	Assignee
Due Date	date	Due Date
Level	text	Level
Camera	text	Camera

LadyBug Tracker uses the Level and Camera properties to keep the position from which you reported a bug. Add these two properties as Text properties. The 3D markers and the Goto button need them.

The Created and Updated fields come from the timestamps of the page. They are always available.

Integration capabilities

Notion does not tell which capabilities an integration has. Thus the plugin tests each capability and shows the result in the settings window.

By default, Notion does not let an integration read comments. Without this capability, the plugin does not read comments, but the rest of the download does not fail. Thus the fields and attachments still load. To enable this capability, open the integration at notion.so/my-integrations. Then give it the read comments capability.

Attachments

The plugin keeps attachments as blocks in the page body (image, video, audio, pdf or file), not in a files property. When the plugin adds an attachment, it does not write the existing blocks again. Thus a different edit at the same time cannot remove earlier attachments.

A free Notion workspace refuses a file that is larger than 5 MB. To prevent this problem, you can set Max Screenshot Size in the project settings. Then the plugin makes large screenshots smaller before it uploads them.

Subtasks

The plugin makes the subtask checklist from the to-do blocks in the page body. A Notion page has no checklist container. Thus all the to-do items of the page are in one checklist with the name Subtasks. You can add, rename, tick and delete items. You cannot make or delete the checklist.

Known limitations

You can add and read comments, but the Notion API cannot delete them.
Issue history and workflow status transitions are not available.
You cannot make a new database from the plugin, because the API cannot select a parent page. First, make the database in Notion.
When you delete an issue, the plugin archives the page. Notion gives this operation in place of a permanent delete.
A plain select property has no completion information. If the completion state is important, use a status property.

Project setup (Unreal Engine)

Open Project Settings > Plugins > LadyBug Tracker. Then do these steps:

Provider — select Notion.
Host — keep https://www.notion.so.
Change Login Settings — paste the internal integration secret.
Project — select the database that you shared with the integration.

The plugin keeps these settings in Config/DefaultBugTracker.ini. You can share them with the team. The plugin keeps the integration secret separately for each user. It keeps the secret only when Remember Me is enabled.