Actions63
- Issue Actions
- Comment Actions
- Cycle Actions
- Cycle 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 "Transfer Issues" operation under the "Cycle" resource allows users to move all issues from one cycle to another within the same project in Plane. This is useful for reorganizing work items when cycles (timeboxed periods or sprints) change, such as when a cycle ends and its unfinished issues need to be moved to a new cycle. For example, if you have a sprint cycle that is completed but some issues remain open, you can transfer those issues to the next sprint cycle to continue tracking their progress.
Properties
| Name | Meaning |
|---|---|
| Project ID | The unique identifier of the project containing the cycles and issues. |
| Cycle ID | The unique identifier of the current cycle from which issues will be transferred. |
| New Cycle ID | The unique identifier of the target cycle to which the issues will be transferred. |
Output
The output JSON contains the response from the Plane API after transferring issues from the source cycle to the target cycle. It typically includes details about the updated cycle or confirmation of the transfer operation. The exact structure depends on the Plane API's response but generally confirms successful issue reassignment.
This node does not output binary data for this operation.
Dependencies
- Requires an active connection to the Plane API with valid authentication credentials (an API key or token).
- The node uses internal helper functions to make HTTP requests to Plane's REST endpoints.
- No additional external services are required specifically for this operation.
Troubleshooting
Common issues:
- Invalid or missing Project ID, Cycle ID, or New Cycle ID parameters will cause the API request to fail.
- Attempting to transfer issues between cycles belonging to different projects is not supported.
- Network or authentication errors may prevent successful API calls.
Error messages:
- Errors returned by the Plane API will be propagated, such as "Cycle not found" or "Unauthorized".
- If the node fails due to missing binary data or other unrelated reasons, it will throw descriptive errors.
Resolution tips:
- Verify that all IDs are correct and correspond to existing entities in Plane.
- Ensure the API credentials used have sufficient permissions to modify cycles and issues.
- Check network connectivity and Plane API status.
Links and References
- Plane API Documentation (for detailed API endpoint info)
- n8n documentation on creating custom nodes