Actions63
- Comment Actions
- Cycle Actions
- Cycle Issue Actions
- Issue Actions
- Issue Attachment Actions
- Issue Property Actions
- Issue Property Option Actions
- Issue Property Value Actions
- Issue State Actions
- Label Actions
- Link Actions
- Member Actions
- Module Actions
- Module Issue Actions
- Project Actions
Overview
The "Add Issues to Cycle" operation in the Cycle Issue resource allows users to add one or more existing issues to a specific cycle within a project. This is useful for organizing and grouping issues into cycles (timeboxed periods or milestones) to better manage development sprints, releases, or phases of work.
Common scenarios include:
- Planning a sprint by adding selected issues to the sprint cycle.
- Grouping related issues under a milestone cycle for tracking progress.
- Managing workload distribution by assigning issues to different cycles.
Practical example:
- A project manager wants to add multiple bug reports and feature requests to the current development cycle. They provide the project ID, the cycle ID representing the current sprint, and a comma-separated list of issue IDs to be included in that cycle.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project containing the cycle and issues. |
| Cycle ID | The unique identifier of the cycle to which issues will be added. |
| Issue IDs | A comma-separated string listing the IDs of the issues to add to the specified cycle. |
Output
The output JSON contains the response from the Plane API after adding the specified issues to the cycle. Typically, this includes details about the cycle issues created or updated, such as their IDs and associated metadata.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Plane API with valid authentication credentials (an API key or token).
- The node depends on the Plane API endpoints for projects, cycles, and cycle-issues.
- Proper configuration of the Plane API credential in n8n is necessary.
Troubleshooting
- Invalid Project or Cycle ID: If the provided project or cycle ID does not exist or is incorrect, the API call will fail. Verify that the IDs are correct and correspond to existing resources.
- Malformed Issue IDs: The issue IDs must be provided as a comma-separated list without extra spaces or invalid characters. Ensure the format is correct.
- Permission Errors: Insufficient permissions on the Plane API side may cause failures. Confirm that the API key has rights to modify cycles and issues.
- Network or API Errors: Temporary network issues or Plane API downtime can cause errors. Retry after some time or check Plane API status.
- Error Messages: The node may throw errors indicating missing parameters or failed API calls. Review error messages carefully and ensure all required fields are set.
Links and References
- Plane API Documentation (general reference for API endpoints)
- n8n documentation on Using API Credentials
- Best practices for managing issues and cycles in Plane (refer to Plane's official user guides)