Use single type of unit in columns #8

Open
opened 2022-05-18 11:37:11 +03:00 by mariuspana · 1 comment
mariuspana commented 2022-05-18 11:37:11 +03:00 (Migrated from github.com)

When listing packages in the creation screen, the disk units switch between GB and TB depending on package's disk size. I think this could potentially cause accidents to anybody not paying attention, so I suggest we stick strictly to a single unit per column (e.g. only GB for the disk column).

When listing packages in the creation screen, the disk units switch between GB and TB depending on package's disk size. I think this could potentially cause accidents to anybody not paying attention, so I suggest we stick strictly to a single unit per column (e.g. only GB for the disk column).
mariuspana commented 2022-06-14 12:20:45 +03:00 (Migrated from github.com)

The confusion is when creating packages, although this concept should prevail project-wide (i.e. everywhhere). I propose we use GB in all cases and avoid showing things in TB or if we do, than maybe this issue is resolved by the remediation of the sorting issues described in issue #11.

Screenshot 2022-06-14 at 12 19 06
The confusion is when creating packages, although this concept should prevail project-wide (i.e. everywhhere). I propose we use GB in all cases and avoid showing things in TB or if we do, than maybe this issue is resolved by the remediation of the sorting issues described in [issue #11](https://github.com/spearheadsys/sc-portal/issues/11). <img width="852" alt="Screenshot 2022-06-14 at 12 19 06" src="https://user-images.githubusercontent.com/5336530/173542778-fc644978-3708-4598-aa45-94dec7ad1ae1.png">
Sign in to join this conversation.
No description provided.