Implement Cancel and Delete order

[shubham-padia]

Resolves #2986 .

[coveralls]

Coverage decreased (-0.2%) to 75.454% when pulling 88b066c on shubham-padia:development into 2633ace on fossasia:development.

[codecov-io]

Current coverage is 75.17% (diff: 17.07%)

Merging #3026 into development will decrease coverage by 0.26%

@@           development      #3026   diff @@
=============================================
  Files              220        220          
  Lines            14889      14930    +41   
  Methods              0          0          
  Messages             0          0          
  Branches             0          0          
=============================================
- Hits             11231      11223     -8   
- Misses            3658       3707    +49   
  Partials             0          0          

Powered by Codecov. Last update b9f7976...0bf86a9

[niranjan94]

@shubham-padia if an already paid for order is cancelled/deleted, how are the refunds handled ?

[shubham-padia]

@niranjan94

if an already paid for order is cancelled/deleted, how are the refunds handled ?

AFAIK we do not have the payment details of the user stored, so nothing for that for now. As an alternative removing/cancelling can be disabled for completed orders. What do you think?

[niranjan94]

@shubham-padia actually, we do store the unique order reference ID from paypal/stripe for each payment. We can initiate refunds via Stripe/PayPal API.

@mariobehling do we need refund functionality or can cancel/delete option be disabled for paid orders. ?

[coveralls]

Changes Unknown when pulling 4387813 on shubham-padia:development into ** on fossasia:development**.

[shubham-padia]

do we need refund functionality or can cancel/delete option be disabled for paid orders. ?

@mariobehling suggestions on what should be done?

[mariobehling]

@mariobehling do we need refund functionality or can cancel/delete option be disabled for paid orders.

For now, disable the delete functionality for these in the system.

@shubham-padia actually, we do store the unique order reference ID from paypal/stripe for each payment. We can initiate refunds via Stripe/PayPal API.

Yes, this is the way to go. Please open an issue, but tag it "later" until we have a more stable release. For now we can simply "cancel" paid tickets if required and tell the user to do the refund through paypal. We have so many areas to take care of and better follow up on this later, I would say.

[coveralls]

Coverage decreased (-0.2%) to 75.454% when pulling e77ec0f on shubham-padia:development into 55249a0 on fossasia:development.

[coveralls]

Changes Unknown when pulling 4342c00 on shubham-padia:development into ** on fossasia:development**.

[coveralls]

Coverage remained the same at 74.988% when pulling 03ebef7 on shubham-padia:development into b58f78f on fossasia:development.

[coveralls]

Coverage decreased (-0.2%) to 74.988% when pulling 03ebef7 on shubham-padia:development into b58f78f on fossasia:development.

[shubham-padia]

@niranjan94 @mariobehling Please review. following are some screenshots:
If the ticket is paid and status is completed it cannot be deleted
1.)

2.)

3.)

4.)

5.)

[coveralls]

Coverage decreased (-0.3%) to 74.943% when pulling dcea3c0 on shubham-padia:development into b9f7976 on fossasia:development.

[coveralls]

Coverage decreased (-0.3%) to 74.943% when pulling dcea3c0 on shubham-padia:development into b9f7976 on fossasia:development.

[coveralls]

Coverage decreased (-0.3%) to 74.943% when pulling dcea3c0 on shubham-padia:development into b9f7976 on fossasia:development.

[coveralls]

Coverage decreased (-0.3%) to 74.943% when pulling 97be717 on shubham-padia:development into b9f7976 on fossasia:development.

[coveralls]

Coverage decreased (-0.3%) to 74.943% when pulling 97be717 on shubham-padia:development into b9f7976 on fossasia:development.

[coveralls]

Coverage decreased (-0.3%) to 74.943% when pulling 0bf86a9 on shubham-padia:development into b9f7976 on fossasia:development.