Guide for developers

Your day in NaatOps

1. Start in My work. The Mine queue shows what's assigned to you, grouped by status, with due dates. Overdue work is marked in red.
2. Open the board of your project. The board shows the active sprint by default. Use All assignees to show only your cards.
3. Move a card when you start, when you raise a pull request and when it's done. Drag it to the next column, or change Status on the issue page.
4. Check your Inbox for mentions, new assignments and comments on issues you watch.

Work on an issue

Open an issue by clicking its card or its key. On the issue page:

• The right-hand panel holds status, assignee, sprint, priority, estimate, labels, due date and more. Click any value to change it.
• Write or update the description. Markdown works: headings, lists, code blocks and tables.
• Relations link this issue to others: blocks, blocked by, related to or duplicate of.
• Quality shows the test cases and API checks that cover the issue and their last result. If a tester found this bug in a run, it says which case and run.
• Comments at the bottom. Type @ and a name to mention someone; they get notified.

See Issues for everything on this page.

Link your code

Put the issue key in your branch name, commit message or pull request title, for example feature/CP-12-otp-login or CP-12: Add OTP login. Once your admin has connected the repository's GitHub webhook, the issue's Development section shows the branches, pull requests (open or merged) and where the code is deployed.

You can also paste a link to a pull request, commit or branch with Link code on the issue page.

Your admin can add automation rules so that opening a pull request moves the issue to In progress, and merging moves it to Done. See Automation rules.

Fix a bug from a test run

When QA marks a test case as failed, they can file a bug from the run with one click. The bug arrives with the case's steps, expected result and what actually happened, and lands in the same sprint. It appears in My work › Bugs and on the board.

Fix it, move it to the review or QA column, and the tester re-runs the case.

Test your API

The project's API tab is a built-in API client. Use it to try your endpoints against dev or staging, save requests in collections and add checks. See API workspace.

Work from your editor

NaatOps has a plugin for Cursor and other MCP-capable editors. It can list your work, create and update issues and add comments for you. Ask your admin for a bot id and key from Settings › Bots, then follow the plugin's setup.