Skip to content

Conversation

@uds5501
Copy link
Contributor

@uds5501 uds5501 commented Jul 12, 2019

Fixes fossasia/open-event-frontend#3269

Short description of what this resolves:

Ensures that deletion of orders doesn't trigger notifications and emails

Checklist

  • I have read the Contribution & Best practices Guide and my PR follows them.
  • My branch is up-to-date with the Upstream development branch.
  • The unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • All the functions created/modified in this PR contain relevant docstrings.

@auto-label auto-label bot added the fix label Jul 12, 2019
@codecov
Copy link

codecov bot commented Jul 12, 2019

Codecov Report

Merging #6184 into development will not change coverage.
The diff coverage is 0%.

Impacted file tree graph

@@             Coverage Diff              @@
##           development    #6184   +/-   ##
============================================
  Coverage        66.13%   66.13%           
============================================
  Files              288      288           
  Lines            14479    14479           
============================================
  Hits              9575     9575           
  Misses            4904     4904
Impacted Files Coverage Δ
app/api/orders.py 31.02% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0a5f6cd...1551de6. Read the comment docs.

@uds5501
Copy link
Contributor Author

uds5501 commented Jul 12, 2019

@mrsaicharan1 @shreyanshdwivedi @prateekj117 Please take a look

@kushthedude
Copy link
Member

@uds5501 , There should be an email to attendee perhaps

@uds5501
Copy link
Contributor Author

uds5501 commented Jul 12, 2019

@kushthedude deletion of an order doesn't change any status so, IMO there should be none.
Deletion of the order is organizer activity and only unpaid or cancelled tickets can be deleted (AFAIK) so attendee discretion isn't really necessary here.

@kushthedude
Copy link
Member

@kushthedude deletion of an order doesn't change any status so, IMO there should be none.
Deletion of the order is organizer activity and only unpaid or cancelled tickets can be deleted (AFAIK) so attendee discretion isn't really necessary here.

Let us take this case, Some user has ordered a bunch of Offline Tickets, Due to some reason Organiser deletes there order, How will the user know his order does not exist now. I totally agree with you that Cancelled or Expired or Pending order should deliver no notification upon deletion .

@uds5501
Copy link
Contributor Author

uds5501 commented Jul 12, 2019

@kushthedude as far as notifying them that their order has been deleted, it'll take a new notification and email.
In this particular issue however, what I am trying to point out is that if we allow this behaviour to persist, the user simply gets notified that that their ticket has been placed instead of deleted. Maybe you can open up a new issue for the one you pointed out.

@iamareebjamal iamareebjamal merged commit f352525 into fossasia:development Jul 12, 2019
iamareebjamal pushed a commit to iamareebjamal/open-event-server that referenced this pull request Aug 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deleting orders trigger notifications and emails

3 participants