Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine

DRC - Design Review Finalization Slack Notification

Open
#2,412 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

front-end medium
Dominant language
TypeScript
Stars
36
Forks
9
Avg merge
4d 21h
Merged PRs (30d)
11

Description

Description

When a DR is finalized, only those who confirm their availability will be notified about the finalized time and place of the meeting. We want to notify the users who didn't confirm their availability (they would be optional members) of the finalization of the DR. This notification should be a ping done in the same thread as the finalization (Essentially it should all be under one thread - the same thread where notifications for people confirming their availability are).

Acceptance Criteria
  • Users who did not confirm their availability and are optional members (This is given as only optional members can't confirm their availability) should be notified via slack about the finalized DR
  • The notification for the ping should be done in the same thread as the DR finalizationSlack
Proposed Solution

Good luck!

Mocks

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the DR finalization Slack notification flow, then trace how confirmed and optional members are selected and how the existing finalization thread is identified. Done means optional members receive the finalized DR notification in that same thread, with coverage for both acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.