Actions6
- Issues Actions
- Pages Actions
- Projects Actions
Overview
The node integrates with Mantis Bug Tracker (MantisBT) to retrieve multiple issues from a specified project. It supports filtering and pagination, allowing users to fetch a customized list of issues based on criteria such as assignment, reporting, or monitoring status.
Common scenarios include:
- Fetching all issues for a project to display in dashboards.
- Retrieving issues assigned to the current user for task management.
- Paginating through large sets of issues to process or analyze them incrementally.
Practical example:
- A project manager wants to get the first 20 issues reported by their team in a specific project to review progress.
- A developer wants to list all unassigned issues to pick new tasks.
Properties
| Name | Meaning |
|---|---|
| Select Fields | Comma-separated list of issue fields to return (e.g., id,summary,description). Leave empty to get all fields. |
| Page Size | Number of issues to return per page. |
| Page Number | The page number to retrieve (for pagination). |
| Project ID | The numeric ID of the project from which to fetch issues. |
| Filter | Predefined filters to apply when fetching issues: - None - Assigned to Me - Reported by Me - Monitored By Me - Unassigned |
Output
The node outputs an array of issue objects in the json field. Each object contains the fields requested via the "Select Fields" property or all available fields if none are specified.
The structure of each issue object corresponds to MantisBT's issue representation, including properties like id, summary, description, and other metadata depending on the selected fields.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a Mantis Bug Tracker instance with REST API enabled.
- Needs an API token credential for authentication.
- The base URL of the MantisBT API must be configured in the node credentials.
- Pagination and filtering depend on the MantisBT API capabilities.
Troubleshooting
Common Issues:
- Incorrect or missing API token will cause authentication failures.
- Invalid project ID may result in empty results or errors.
- Using unsupported field names in "Select Fields" can lead to incomplete data or API errors.
- Network connectivity issues to the MantisBT server.
Error Messages:
- Authentication errors typically indicate invalid or expired API tokens; verify and update credentials.
- "Project not found" or similar errors suggest the project ID does not exist or is inaccessible.
- Rate limiting or timeout errors require checking server availability and possibly adjusting request frequency.