MantisBT
Developer ToolsMantisBT is the open-source, self-hosted bug tracker. Agents create, update, and move issues, add notes, attachments, tags, and relationships, and manage projects, versions, and users over the built-in REST API.
What This Integration Enables
MantisBT is the bug tracker you run on your own hardware, and that is the whole point of it. Nobody picks a self-hosted tracker by accident. They pick it because the defect data describes systems they are not willing to host elsewhere, or because the instance has been shaped over years into something that matches how the team actually works. Both of those choices have a consequence for automation: the rules are yours, not the vendor's. Categories are defined per project. Status, priority, and severity are enumerations the administrator can rewrite. There is no per-field issue search over the REST API at all, so a saved filter's id is the query language.
That is why FlowRunner agents read this instance before they write to it. Connectors here cover the full working surface: filing and updating issues, moving them between projects, attaching files and notes, managing tags and relationships, running the projects, versions, and membership underneath, and reading the configuration that explains why a write was refused. The agent does the retyping, the lookups, and the evidence gathering. Where a write would quietly discard data or quietly change who can sign in, FlowRunner's human-in-the-loop discipline puts a person in front of it.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Support defects arrive as complete issues
A ticket in Zendesk or Freshdesk gets tagged as a defect. The agent calls List Projects to read the target project's categories and versions, because a category that exists in one project is rejected in another and the error does not explain itself. It calls List Project Handlers to confirm the intended assignee is above the handler access level, which is the other rejection nobody can diagnose from the message. Create Issue files the defect. Add Attachment pulls the customer's log file straight from the ticket by URL and MantisBT stores it. Add Note records the ticket reference and the account. The support agent gets the issue number back in the ticket thread, and the developer opens a record that already contains everything.
-
The changelog that builds itself
When a build ships, the agent calls Create Version on the affected project, then walks the issues marked fixed in that build with List Issues against a saved filter. It confirms each one's Fixed In Version, then calls Update Version to set Released. That last call is the step that matters: MantisBT builds its changelog from issues whose Fixed In Version points at a released version, so a version left unreleased produces an empty changelog no matter how many issues reference it. The release notes then post to Slack and the linked build in Jenkins or GitHub gets a comment naming the issues it closed.
-
Offboarding that keeps the history readable
A departure notice reaches the agent. It calls Get User By Username to resolve the account, List Project Users across the projects they touched, and Delete User Token to cut off any automation running as them, which is the part with no downside. Then it stops. Deleting the account itself would leave every note and issue they ever wrote attributed to a bare numeric placeholder, permanently. The agent proposes Update User with Enabled set to false instead, which suspends the account and keeps the attribution intact, and lets the administrator confirm which one they want.
Human-in-Loop Highlight
Move Issue looks like a filing correction and behaves like a partial delete. An issue's category, its Product Version and Target Version, and its custom field values all belong to the project it currently lives in. When MantisBT moves the issue somewhere else, it remaps what the target project also has and drops the rest. The call succeeds. Nothing reports what was discarded. So a triage agent that has decided a bug was filed against the wrong component gathers the evidence and then stops: "Issue 4182 is filed in Mobile Client and reads like a defect in Sync Service. Moving it drops Target Version 3.4, the category Crash, and two custom fields that Sync Service does not define. Move it, or file a linked issue in Sync Service and close this one as a duplicate?" The engineering lead answers. What made the routing safe was not the agent's reading of the bug report. It was that the operation which silently destroys context belonged to a person who could weigh what was being lost.
Agent Capabilities
54 actionsIssues
8- List Issues Returns the issues visible to the connection's user. MantisBT exposes no per-field search over REST, so anything narrower than a whole project means naming a saved filter or one of the built-ins.
- Get Issue Returns a single issue with its notes, attachments, tags, relationships, and history. The response carries the ETag that makes a later update or delete safe against a concurrent edit.
- Create Issue Files a new issue. Summary, description, project, and category are all required in practice, and categories are per project.
- Update Issue Applies changed fields to an issue. Supplying the ETag from Get Issue makes MantisBT refuse rather than overwrite somebody else's edit.
- Delete Issue Permanently removes an issue with its notes, attachments, and history. There is no trash. Closing the issue is almost always what a workflow means.
- Move Issue Moves an issue into a different project. Anything the target project does not define is dropped, which is why this page's human gate exists.
- Monitor Issue Sets who receives MantisBT's change emails for an issue. It replaces the monitor list rather than adding to it.
- Get Issue View Page Returns an issue together with the status transitions this user may make and the fields they may edit. The way a workflow acts on real permissions instead of guessing and getting refused.
Notes
2- Add Note Appends a note to an issue and emails whoever is monitoring it. The view state decides whether reporters can read it, so agents set it deliberately.
- Delete Note Removes a note. Permanent, and the history records only that something was deleted.
Attachments
4- Add Attachment Attaches a file to an issue. Pass a file URL and the connector fetches and encodes it, which is what a workflow carrying a log or a screenshot from an earlier step needs.
- List Attachments Returns an issue's attachments with names, sizes, and content types, without the file bytes.
- Get Attachment Fetches one attachment into FlowRunner file storage and returns a URL later steps can use.
- Delete Attachment Removes an attachment and the stored file with it.
Tags and Relationships
4- Add Tags Attaches tags to an issue additively, unlike sending tags through Update Issue, which replaces them.
- Remove Tag Detaches one tag from an issue. The tag itself survives.
- Add Relationship Relates one issue to another. MantisBT adds the mirrored relationship automatically, so adding both by hand creates a duplicate pair.
- Delete Relationship Removes a relationship and its mirror.
Projects
5- List Projects Returns the projects the user can see, each with its categories, versions, and custom field definitions. The lookup to run before any create.
- Get Project Returns one project with its categories, versions, subprojects, and custom fields.
- Create Project Creates a project. A new project has no categories, and MantisBT refuses an issue without one, so the first filing fails until a category exists.
- Update Project Changes a project's settings, including whether it is enabled. The reversible alternative to deleting one.
- Delete Project Permanently deletes a project along with every issue, note, and attachment inside it.
Versions
5- List Versions Returns a project's versions. These are the only values the version fields on an issue will accept.
- Get Version Returns one version of a project.
- Create Version Adds a version to a project. The first half of a release workflow.
- Update Version Changes a version, including marking it released. Setting Released is what makes the changelog populate.
- Delete Version Removes a version. Issues that referenced it keep the now dangling name rather than being cleared.
Subprojects
3- Add Subproject Makes an existing project a subproject of another. Both must already exist.
- Update Subproject Changes whether a subproject inherits its parent's categories and configuration.
- Delete Subproject Removes the parent and child link. Neither project is deleted.
Project Membership
5- List Project Users Returns the users with access to a project and their access levels.
- List Project Handlers Returns the users who may actually be assigned issues in a project. The check that prevents an unexplained rejection on assignment.
- Add Project User Grants a user access to a project at a chosen level. Fails if they are already a member.
- Set Project User Adds a user to a project or updates an existing member's level. The idempotent form, and the one a workflow should use.
- Remove Project User Removes an explicit membership. A user whose global access level already reaches the project keeps it.
Users
8- Get My User Returns the user the token belongs to. The cheapest way to confirm the instance URL, the token, and that the REST API is switched on.
- List Users Returns the instance's users. Administrator access only.
- Get User Returns one user by numeric id.
- Get User By Username Looks a user up by login name, which is usually all a workflow knows. Usernames are case sensitive on most installs.
- Create User Creates an account. MantisBT normally emails a password link rather than accepting a password here, so an instance that cannot send mail creates an account nobody can use.
- Update User Changes an account, including disabling it. Disabling suspends access while keeping the person's history attributed to them.
- Delete User Permanently removes an account. Their issues and notes remain but lose their author.
- Reset User Password Triggers MantisBT's own password reset email for a user.
API Tokens
4- Create My Token Issues an API token for the current user. The value is returned once and stored only as a hash.
- Create User Token Issues a token on another user's behalf. It acts as that person, so the response is a credential.
- Delete My Token Revokes a token belonging to the current user, including possibly the one in use.
- Delete User Token Revokes another user's token. The offboarding step that cuts a departing employee's automation without touching their history.
Saved Filters
3- List Filters Returns the saved filters available to the user. Since MantisBT has no field search over REST, a filter id is the query.
- Get Filter Returns one saved filter with its criteria.
- Delete Filter Removes a saved filter. Deleting a public one removes it for everybody, and workflows using its id start returning everything in scope.
Configuration
3- Get Configuration Returns configuration option values, including the status, priority, severity, and resolution enumerations this instance actually uses. The answer to why a write was refused.
- Set Configuration Sets configuration options. This changes the whole installation's behavior, needs administrator access, and MantisBT validates very little of it.
- Get Localized Strings Returns MantisBT's own translated interface strings, so a composed message matches the labels users see.
Frequently Asked Questions
What can FlowRunner do with MantisBT?
FlowRunner agents can run List Issues, Get Issue, and Create Issue in MantisBT, plus 51 more actions.
Does connecting MantisBT to FlowRunner require OAuth?
No. MantisBT connects to FlowRunner with an API key, no OAuth flow required.
Can MantisBT trigger a FlowRunner workflow automatically?
MantisBT doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Developer Tools integrations
Start building with MantisBT
Free plan, no card required. Connect in minutes.