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

Remove date ranges for config options

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.6.0
    • Fix Version/s: Sponsored, 4.8.0-b1
    • Component/s: Plugins
    • Labels:
      None

      Description

      When ordering configurable options, the covered date range is displayed in the order summary box, but these dates are always the same as the parent and are shown for the parent already. Also, since the description of configurable options can be long, it can get overwhelming and difficult to follow.

      Let's remove the date range shown for configurable options, since it is shown already for the parent. So, instead of this:

      Test Package (Jul 30, 2019 - Aug 30, 2019) 1 @ $5.00
      -> Email Addresses - 5x How many emails? (Jul 30, 2019 - Aug 30, 2019) 5 @ $2.50

      We would show this:

      Test Package (Jul 30, 2019 - Aug 30, 2019) 1 @ $5.00
      -> Email Addresses - 5x How many emails? 5 @ $2.50

      See screenshot for details.

        • Add a setting to denote whether to remove verbose dates from config options on invoices/orders
        • Remove dates from the config options iff there is a parent service item. That is, if there is no parent service item, which may be the case when updating an existing service to add a new config option, the new config option may appear alone on the invoice, so we would want to display the date in that case.

        Activity

        admin Paul Phillips created issue -
        Hide
        tyson Tyson Phillips (Inactive) added a comment -

        What if you add a config option to an existing service or it's prorated? It may not be clear why it said it cost $5 but is really only $1.27 (because of proration) without seeing the date range is not exactly a month. It seems like this may be better as a configurable option in some way.

        Show
        tyson Tyson Phillips (Inactive) added a comment - What if you add a config option to an existing service or it's prorated? It may not be clear why it said it cost $5 but is really only $1.27 (because of proration) without seeing the date range is not exactly a month. It seems like this may be better as a configurable option in some way.
        Hide
        jonathan Jonathan Reissmueller added a comment -

        When we look into this, Blesta\Core\Pricing\Modifier\Type\Description\Type\Option::getOption() is where we should start

        Show
        jonathan Jonathan Reissmueller added a comment - When we look into this, Blesta\Core\Pricing\Modifier\Type\Description\Type\Option::getOption() is where we should start
        tyson Tyson Phillips (Inactive) made changes -
        Field Original Value New Value
        Rank Ranked lower
        Hide
        admin Paul Phillips added a comment -

        Approved for 4.8. Assuming this will impact invoices also, which is what we want.

        Show
        admin Paul Phillips added a comment - Approved for 4.8. Assuming this will impact invoices also, which is what we want.
        tyson Tyson Phillips (Inactive) made changes -
        Rank Ranked higher
        tyson Tyson Phillips (Inactive) made changes -
        Description When ordering configurable options, the covered date range is displayed in the order summary box, but these dates are always the same as the parent and are shown for the parent already. Also, since the description of configurable options can be long, it can get overwhelming and difficult to follow.

        Let's remove the date range shown for configurable options, since it is shown already for the parent. So, instead of this:

        Test Package (Jul 30, 2019 - Aug 30, 2019) 1 @ $5.00
        -> Email Addresses - 5x How many emails? (Jul 30, 2019 - Aug 30, 2019) 5 @ $2.50

        We would show this:

        Test Package (Jul 30, 2019 - Aug 30, 2019) 1 @ $5.00
        -> Email Addresses - 5x How many emails? 5 @ $2.50

        See screenshot for details.
        When ordering configurable options, the covered date range is displayed in the order summary box, but these dates are always the same as the parent and are shown for the parent already. Also, since the description of configurable options can be long, it can get overwhelming and difficult to follow.

        Let's remove the date range shown for configurable options, since it is shown already for the parent. So, instead of this:

        Test Package (Jul 30, 2019 - Aug 30, 2019) 1 @ $5.00
        -> Email Addresses - 5x How many emails? (Jul 30, 2019 - Aug 30, 2019) 5 @ $2.50

        We would show this:

        Test Package (Jul 30, 2019 - Aug 30, 2019) 1 @ $5.00
        -> Email Addresses - 5x How many emails? 5 @ $2.50

        See screenshot for details.

        ** Add a setting to denote whether to remove verbose dates from config options on invoices/orders
        ** Remove dates from the config options iff there is a parent service item. That is, if there is no parent service item, which may be the case when updating an existing service to add a new config option, the new config option may appear alone on the invoice, so we would want to display the date in that case.
        tyson Tyson Phillips (Inactive) made changes -
        Summary Order: Do not display date ranges for config options in order summary Do not display date ranges for config options in order summary
        tyson Tyson Phillips (Inactive) made changes -
        Summary Do not display date ranges for config options in order summary Remove date ranges for config options
        tyson Tyson Phillips (Inactive) made changes -
        Sprint 4.8.0 Sprint 2 [ 93 ]
        tyson Tyson Phillips (Inactive) made changes -
        Rank Ranked higher
        tyson Tyson Phillips (Inactive) made changes -
        Story Points 5
        tyson Tyson Phillips (Inactive) made changes -
        Story Points 5 3
        tyson Tyson Phillips (Inactive) made changes -
        Assignee Tyson Phillips [ tyson ]
        tyson Tyson Phillips (Inactive) made changes -
        Fix Version/s 4.8.0-b1 [ 11127 ]
        tyson Tyson Phillips (Inactive) made changes -
        Assignee Tyson Phillips [ tyson ]
        Automated transition triggered when Tyson Phillips (Inactive) created a branch in Stash -
        Status Open [ 1 ] In Progress [ 3 ]
        Automated transition triggered when Tyson Phillips (Inactive) created pull request #748 in Stash -
        Status In Progress [ 3 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        tyson Tyson Phillips (Inactive) made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 5 hours, 26 minutes [ 19560 ]
        Worklog Id 12670 [ 12670 ]
        jonathan Jonathan Reissmueller made changes -
        Time Spent 5 hours, 26 minutes [ 19560 ] 6 hours, 17 minutes [ 22620 ]
        Worklog Id 12672 [ 12672 ]
        Automated transition triggered when Tyson Phillips (Inactive) merged pull request #748 in Stash -
        Status In Review [ 5 ] Closed [ 6 ]
        tyson Tyson Phillips (Inactive) made changes -
        Link This issue Testing discovered CORE-3351 [ CORE-3351 ]

          People

          • Assignee:
            tyson Tyson Phillips (Inactive)
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              23/Dec/19

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 6 hours, 17 minutes
              6h 17m

                Agile