fix: unable to added issues to a completed cycle

[henit-chobisa]

Tasks

• Removed code that was preventing to add issues to cycle which has been completed.

Summary by CodeRabbit

• New Features

  • Users can now add new issues to cycles even after they have been marked as completed.

• Bug Fixes

  • Removed restriction that previously prevented adding issues to completed cycles, addressing the 400 Bad Request error.

[coderabbitai]

Walkthrough

The change in the Cycle view’s post method allows new issues to be added to cycles that have already been completed, as it removes the previous validation check for the end_date. This modification enhances the flexibility of cycle management, enabling users to modify cycles regardless of their completion status, thereby streamlining workflows.

Changes

File	Change Summary
apiserver/plane/api/views/cycle.py	Removed validation for end_date in the post method, allowing addition of issues to completed cycles.

Poem

In the meadow bright and wide,
A cycle's end we used to bide.
Now with joy, we can amend,
Add new issues, our cycles blend!
Hop along, let's celebrate,
For changes made, oh, isn’t it great! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 269e6cc and a93e13f.

Files selected for processing (1)

• apiserver/plane/api/views/cycle.py (1 hunks)

Additional comments not posted (1)

apiserver/plane/api/views/cycle.py (1)

Line range hint 146-146:
Verify the impact of removing the end_date validation.

The removal of the end_date validation check allows issues to be added to completed cycles. Ensure that this change does not introduce unintended side effects or security issues. Verify that the corresponding tests and documentation are updated to reflect this new behavior.