8000 feat: reporting when opportunity is broken/closed/duplicated ❗️ by ramiAbdou · Pull Request #726 · colorstackorg/oyster · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat: reporting when opportunity is broken/closed/duplicated ❗️ #726

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 6 commits into from
Mar 5, 2025
Merged

feat: reporting when opportunity is broken/closed/duplicated ❗️ #726

merged 6 commits into from
Mar 5, 2025

Conversation

ramiAbdou
Copy link
Member
@ramiAbdou ramiAbdou commented Mar 5, 2025 •
edited
Loading

Description ✏️

This PR supports the ability to report an opportunity as closed/duplicated/broken link.

  • Adds the opportunity_reports table including a reason for reporting.
  • Adds a "Report Opportunity" button in the individual opportunity modal, which allows you to select a reason.
  • If an opportunity is reported by 2 people OR an admin, the opportunity will be marked as expired and thus taken off the board.
  • Also removes the not null constraint from the slack_channel_id and slack_message_id on the opportunities table.
  • Updates the seed script to include companies and opportunities (and their related data).

Type of Change 🐞

  • Feature - A non-breaking change which adds functionality.
  • Fix - A non-breaking change which fixes an issue.
  • Refactor - A change that neither fixes a bug nor adds a feature.
  • Documentation - A change only to in-code or markdown documentation.
  • Tests - A change that adds missing unit/integration tests.
  • Chore - A change that is likely none of the above.

Checklist ✅

  • I have done a self-review of my code.
  • I have manually tested my code (if applicable).
  • I have added/updated any relevant documentation (if applicable).

@ramiAbdou ramiAbdou self-assigned this Mar 5, 2025
@ramiAbdou ramiAbdou marked this pull request as ready for review March 5, 2025 00:17
@ramiAbdou ramiAbdou merged commit 38276d9 into main Mar 5, 2025
1 check passed
@ramiAbdou ramiAbdou deleted the rami/opportunities branch March 5, 2025 00:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@ramiAbdou ramiAbdou

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@ramiAbdou
0