Ft notifications tickets cycle #135
Open
+279
−82
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ulse-bn into ft-notifications-tickets-cycle
…ulse-bn into ft-notifications-tickets-cycle
…ulse-bn into ft-notifications-tickets-cycle
…o ft-application-stage
…/atlp-devpulse-bn into ft-notifications-tickets-cycle
…o ft-application-stage
…o ft-application-stage
…/atlp-devpulse-bn into ft-notifications-tickets-cycle
…/atlp-devpulse-bn into ft-notifications-tickets-cycle
iChris-tian
force-pushed
the
ft-notifications-tickets-cycle
branch
from
1a43252
to
d2b29c4
Compare
…ulse-bn into ft-notifications-tickets-cycle
…o ft-application-stage
Aime-Patrick
reviewed
Nov 8, 2024
…/atlp-devpulse-bn into ft-notifications-tickets-cycle
berniceu
approved these changes
Nov 8, 2024
MUNYESHURImanzi
approved these changes
Nov 11, 2024
SHYAKA-Aime
approved these changes
Nov 11, 2024
|
Resolve conflicts |
added 2 commits
November 13, 2024 13:08
…e-bn into ft-notifications-tickets-cycle
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Description
This PR allows users to receive in-app notifications and email notifications about their tickets and changes in their application stage.
Description of tasks that were expected to be completed
As an applicant I want to receive both in-app and email notifications when an action has been taken on my application.
User is notified when:
How has this been tested?
ft-notifications-tickets-cycle.env.examplenpm install, thennpm run devto check if the app is running successfullyTrack PR (issue number & link)
Issue: #216
Screenshots (If appropriate especially on the frontend)
N/A