Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-2472

Renewals should not increment coupon usage when limits don't apply

        Details

        • Type: Improvement
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: None
        • Fix Version/s: 4.2.0-b1
        • Component/s: None
        • Labels:
          None

          Description

          Currently if a coupon is assigned to a service, the coupons usage is incremented when first applied and on every subsequent renewal. This makes sense if the 'Limitations do apply to renewals' option is selected for the coupon, since a renewal is considering usage limit. But when the 'Limitations do not apply to renewals' option is selected, the usage should only incremented for the initial coupon application.

            Issue Links

            relates to

            Improvement - An improvement or enhancement to an existing feature or task. CORE-2468 Expired/Over qty coupons break service modifications

            • Major - Major loss of function.
            • Closed

              Activity

              Hide
              Permalink
              admin Paul Phillips added a comment -

              Also make sure that when "Limitations do not apply", it not only does not decrement the coupon quantity, but that it does not evaluate the quantity or date limitation for renewing services. There is some confusion whether it may be evaluating one or both of those things when it shouldn't.

              Show
              admin Paul Phillips added a comment - Also make sure that when "Limitations do not apply", it not only does not decrement the coupon quantity, but that it does not evaluate the quantity or date limitation for renewing services. There is some confusion whether it may be evaluating one or both of those things when it shouldn't.

                People

                • Assignee:
                  jonathan Jonathan Reissmueller
                  Reporter:
                  jonathan Jonathan Reissmueller
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:
                    Fix Release Date:
                    5/Dec/17

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 37 minutes
                    37m

                      Agile