Uploaded image for project: 'Cost Management'
  1. Cost Management
  2. COST-1173

UI doesn't display correct suborgs/accounts when group_by org. units is applied

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • 2021Q1
    • None
    • UI
    • None
    • False
    • False
    • Undefined

      When org. units group_by is applied, UI should display the suborgs/accounts below the specified org. unit.

      Example using cost_aws_org_unit_crud_source fixture (data can be loaded into ci env upon request):

      Root org. unit id QE_R_001 (alias QE Root) has 2 suborgs and 1 account (see org_unit_hierarchy.png and org_unit_api.png):

      • org. unit id QE_OU_001, alias Dept QE_OU_001 (Rename)
      • org. unit id QE_OU_002, alias Dept QE_OU_002
      • account id 8888888888880, alias QE Root A Test

      When group_by[org. unit] = "QE Root" is applied in UI, it shows only one item "Dept QE_OU_002 (id QE_OU_001)" instead of 3 expected items (see org_units.png)

       

      Api calls used in example:

      /api/cost-management/v1/reports/aws/costs/?filter[time_scope_units]=month&filter[time_scope_value]=-1&filter[resolution]=monthly&group_by[org_unit_id]=QE_R_001

      /api/cost-management/v1/organizations/aws/?filter[time_scope_units]=month&filter[time_scope_value]=-1&filter[resolution]=monthly

      UI api call:

      /api/cost-management/v1/reports/aws/costs/?delta=cost&filter[limit]=10&filter[offset]=0&filter[resolution]=monthly&filter[time_scope_units]=month&filter[time_scope_value]=-1&group_by[org_unit_id]=QE_R_001&order_by[cost]=desc

       

       

        1. org_units.png
          org_units.png
          44 kB
        2. org_unit_api.png
          org_unit_api.png
          51 kB
        3. org_unit_hierarchy.png
          org_unit_hierarchy.png
          55 kB

            dlabrecq@redhat.com Daniel Labrecque
            rhn-support-esebesto Eva Šebestová
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: