-
Notifications
You must be signed in to change notification settings - Fork 129
fix(task): resolve feedback notification issue #52
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.
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
base: 9.x
Are you sure you want to change the base?
fix(task): resolve feedback notification issue #52
Conversation
Fixed an issue where feedback notifications were not sent when task status updated. Now, emails are correctly triggered based on status changes.
martindolores
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good so far! Able to replicate testing steps for the required outcome but some things to note here 🤘
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not 100% sure if this file (Gemfile.lock) should be committed - please double check this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes in Gemfile.lock weren't intentionally added by me - they were automatically generated when I ran the app locally. These changes add x86_64-Linux platform support alongside the existing aarch64 platform.
From what I understand, this is generally beneficial as it expands compatibility to both architectures, but I wanted to confirm if this aligns with our project standards before committing these changes. If preferred, I can revert these Gemfile.lock changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What you say seems good to me! Lets double check with Nebula tomorrow during standup but that sounds fine :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These packages are present in upstream
I recommend merging your branch with 8.0.x and changing the base branch on this PR to 8.0.x
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @b0ink I have created a new pull request as suggested from 8.0.x branch. https://github.com/thoth-tech/doubtfire-api/pull/55/files
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @amriith 😄, you can changes the base branch on this PR as so without having to open up a new PR:


It also looks like some files that you have removed has been added in and some merge conflicts on the other PR:

I suggest to just close the other PR and change the base branch on this to 8.0x. Note that you will have to merge 8.0x to this branch (just run git merge 8.0x and fix any conflicts)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a config file - changes to this are typically not something you would commit unless they are part of a necessary configuration
If testing your changes, just leave in local repo without committing i.e. dont include in this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've removed the configuration file from this PR as suggested, Thanks for letting me know.
Co-authored-by: Martin Dolores <77220115+martindolores@users.noreply.github.com>
amriith
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Made all the mentioned changes in development.rb and task.rb file
|
Base branch changed and merged current branch to 8.0.x |
martindolores
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work! 🕺
AB-Deakin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and working correctly. Peer Review approved by Alex Brown
|
Please resolve conflicts and take the PR through the review process (2 peers, followed by 1 senior leader) again. |
|
Hi @AB-Deakin @martindolores , |
|
Hi @amriith I've gone over the changes and tested and no issues with running it and code looks all good from my checks peer review approved |
AB-Deakin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @amriith I've gone over the changes and tested and no issues with running it and code looks all good from my checks peer review approved
martindolores
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @amriith, changes look good to me. No issues running this 🙂
|
LGTM. |
|
Hi @aNebula Opened a new pr on doubtfire-lms/doubtfire-api with 9.x branch url- doubtfire-lms#471 |
Description
Fixed an issue where feedback notifications were not sent when task status updated. Now, emails are correctly triggered based on status changes.
Fixes # (issue)
Fixes the Notification Mailer feature which notify students if the task status is changed into either of these (redo, fail, fix_and_resubmit, feedback_exceeded, discuss, demonstrate, complete)
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:
If you have any questions, please contact @macite or @jakerenzella.