You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dlab.apache.org by "Vira Vitanska (Jira)" <ji...@apache.org> on 2020/04/14 17:39:00 UTC
[jira] [Updated] (DLAB-1719) Issues with billing export
[ https://issues.apache.org/jira/browse/DLAB-1719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vira Vitanska updated DLAB-1719:
--------------------------------
Description:
*Preconditions:*
1. Billing is available for remote AWS/Azure and local GCP endpoint
*Step to reproduce:*
# Export billing via DLab UI
# Open file
*Actual result:*
# Status column is absent in exporting file
# Instance size is absent in exporting file
# Value of total is absent
# All values in "Resource type" are in upper case
*Expected result:*
# Status column is present in exporting file
# Instance size is present in exporting file
# Value of total is present in exporting file
# Only the first letter of the word is in upper case in "Resource type" column
----
[~ofuks] 1. Should we add user column during export if user is allowed only to view his billing?
2. Should we export sorting data if they are sorted in Billing report? Because now they are exported without sorting.
was:
*Preconditions:*
1. Billing is available for remote AWS/Azure and local GCP endpoint
*Step to reproduce:*
# Export billing via DLab UI
# Open file
*Actual result:*
# Status column is absent in exporting file
# Instance size is absent in exporting file
# Value of total is absent
# All values in "Resource type" are in upper case
*Expected result:*
# Status column is present in exporting file
# Instance size is present in exporting file
# Value of total is present in exporting file
# Only the first letter of the word is in upper case in "Resource type" column
----
[~ofuks] Should we add user column during export if user is allowed only to view his billing?
> Issues with billing export
> --------------------------
>
> Key: DLAB-1719
> URL: https://issues.apache.org/jira/browse/DLAB-1719
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Main
> Reporter: Vira Vitanska
> Assignee: Oleg Fuks
> Priority: Minor
> Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat
> Fix For: v.2.3
>
>
> *Preconditions:*
> 1. Billing is available for remote AWS/Azure and local GCP endpoint
> *Step to reproduce:*
> # Export billing via DLab UI
> # Open file
> *Actual result:*
> # Status column is absent in exporting file
> # Instance size is absent in exporting file
> # Value of total is absent
> # All values in "Resource type" are in upper case
> *Expected result:*
> # Status column is present in exporting file
> # Instance size is present in exporting file
> # Value of total is present in exporting file
> # Only the first letter of the word is in upper case in "Resource type" column
> ----
> [~ofuks] 1. Should we add user column during export if user is allowed only to view his billing?
> 2. Should we export sorting data if they are sorted in Billing report? Because now they are exported without sorting.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@dlab.apache.org
For additional commands, e-mail: dev-help@dlab.apache.org