Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine
Initializing a CR should send a message in the system channel
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
Description
Description
When a Change Request (CR) is initialized in a certain system, a message should be sent in that system's channel confirming that the CR was iniitialized.
Acceptance Criteria
- When any CR is initialized in a system, a message is sent in that system's channel with relevant information
- No other functionalities are affected
- the UI is not affected
Proposed Solution
Find the function that handles the initialization of CRs, and add this functionality into that. If you are unsure of how to implement this functionality, check out how slack messages are sent in other parts of the website.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the function that handles Change Request initialization, then read the existing Slack-message implementations elsewhere in the website. Add a confirmation message to the initialized CR's system channel without changing the UI or other functionality. Verify that every CR initialization sends relevant information to the correct channel.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100