[WEB-2759] fix: intake issue permission

[anmolsinghbhatia]

Changes:

This PR resolves a bug with intake issue permissions where users with member-level permissions couldn't edit their own issue immediately after creation without refreshing the page.

Reference:

[WEB-2759]

Summary by CodeRabbit

• Bug Fixes
  • Corrected the logic for determining the editability of inbox issues, ensuring proper access to the nested issue property.

These changes enhance the accuracy of the inbox functionality, improving user experience when editing issues.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes in this pull request focus on modifying the logic for determining the editability of an inbox issue within the InboxContentRoot component. The condition for the isEditable variable has been updated to check inboxIssue?.issue.created_by instead of inboxIssue?.created_by. This adjustment refines the editability logic while maintaining the existing component structure, including state management and data fetching mechanisms.

Changes

File Path	Change Summary
web/core/components/inbox/content/root.tsx	Modified isEditable logic to check inboxIssue?.issue.created_by instead of inboxIssue?.created_by.

Possibly related PRs

• [WEB-2622] fix: intake exception error #5810: This PR updates the isEditable logic in the InboxContentRoot component, ensuring it checks the inboxIssue?.issue.created_by, which aligns with the changes in the main PR.
• [WEB-2713] fix: guest user intake issue edit validation #5898: This PR also alters the isEditable logic to reference the nested issue property, directly relating to the changes made in the main PR regarding editability checks.

Suggested labels

🐛bug

Suggested reviewers

• sriramveeraghanta
• SatishGandham

🐰 In the inbox where issues reside,
A tweak was made, oh what a ride!
From created_by to issue we peek,
Now editability's logic is sleek.
With hooks in place, the flow stays bright,
Hopping along, all feels just right! 🌟

Warning

Rate limit exceeded

@anmolsinghbhatia has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 6 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between da00712 and 736a758.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between da00712 and 736a758.

📒 Files selected for processing (1)

• web/core/components/inbox/content/root.tsx (1 hunks)

---

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.