Actions50
- Branch Actions
- Commit Actions
- Issue Actions
- Project Actions
- Pull Request Actions
- Repository Actions
- Tag Actions
- File Actions
- User Actions
- Webhook Actions
Overview
This node integrates with the Bitbucket Data Center API to manage various resources such as projects, repositories, pull requests, branches, commits, users, tags, files, webhooks, and issues. Specifically for the Issue resource, it provides operations like create, get, update, and delete.
However, issue operations are not directly supported in Bitbucket Data Center itself. Instead, the node throws an error advising to use Jira integration for issue management. This means that while the node exposes issue-related operations in its interface, attempting to perform these operations will result in an error indicating that Bitbucket Data Center does not support them natively.
Practical Use Case for Delete Issue Operation
- The "Delete" operation under the "Issue" resource is intended to remove an issue from a repository.
- Since Bitbucket Data Center does not support this directly, users should integrate with Jira or another issue tracking system connected to their Bitbucket environment to manage issues.
- This node can be used effectively for other resources like managing repositories, pull requests, branches, etc., but for issues, external integration is required.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: either "Personal Access Token" or "Basic Auth". |
| Project | The project key to work with. Loaded dynamically from available projects. Required. |
| Repository | The repository slug within the selected project. Loaded dynamically based on project. Required. |
| Issue ID | The numeric ID of the issue to operate on. Required for get, update, and delete operations. |
Output
- The output is a JSON array containing the response from the Bitbucket Data Center API for the requested operation.
- For the "Delete" operation on an issue, since it is unsupported, the node throws an error instead of returning data.
- For other resources and operations, the output typically contains the API response object or a success confirmation object like
{ success: true }. - No binary data output is involved in the issue delete operation.
Dependencies
- Requires access to a Bitbucket Data Center server URL.
- Requires credentials for authentication, either via a personal access token or basic authentication.
- The node uses n8n's built-in request helper with authentication to communicate with the Bitbucket Data Center REST API.
- For issue operations, since Bitbucket Data Center does not support them, integration with Jira or another issue tracker is necessary outside this node.
Troubleshooting
Error:
Issue operations are not directly supported in Bitbucket Data Center. Please use Jira integration instead.
Cause: Attempting to perform issue operations (create, get, update, delete) directly on Bitbucket Data Center.
Resolution: Use Jira integration nodes or APIs to manage issues linked to Bitbucket projects.API Request Failures: Errors like
Bitbucket Data Center API request failed: <message>indicate network issues, invalid credentials, or incorrect API endpoints.
Resolution: Verify credentials, server URL, and network connectivity.Missing Required Parameters: If required parameters like Project, Repository, or Issue ID are missing, the node will throw errors.
Resolution: Ensure all required fields are correctly set before execution.
Links and References
- Bitbucket Data Center REST API Documentation
- Jira Integration for Issue Tracking
- n8n Documentation - HTTP Request Node (for understanding API calls)
This summary focuses on the "Issue" resource with the "Delete" operation as requested. The node does not support direct issue management in Bitbucket Data Center and advises using Jira integration instead.