835940 - Data usage graph scaling should adjust at regular intervals

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::Cost Control, defect)

Description

[marcoc]

The data usage graph should scale and adjust at regular intervals to allow better legibility and consistency of visualization. 
current - Currently the graph automatically scales based on the data alert level set by user, and if this number is not even, the graph scales itself in irregular increments that are difficult for a user to understand. 
expected:
- Graph always maintains a regular scale, meaning the numbers on the side always represent an  even scale with round numbers.
- When data level goes beyond the highest limit, the graph adds one horizontal line on top and scales itself to fit the data.
- There should be a maximum of 7 horizontal lines allowed, beyond which the graph goes back to 4 lines and numbers change on the sides.

Comment 1

[marcoc]

Attachment: Expected behavior on horizontal scaling of graph

Comment 2

[marcoc]

Attachment: Expected behavior on horizontal scaling of graph 2

Comment 5

[Salvador de la Puente González [:salva]]

Nit: it refers to the horizontal lines but it is the **vertical** scaling what should be "fixed".

Comment 7

[Salvador de la Puente González [:salva]]

Walter commented something to take in count:

b. Should it show 100KB or 102.4KB?
    Yes, I know this question is so stupid. And, you might think that it's fine to go beyond a little bit or stay in for 2.4KB. However, try to think about data roaming internationally, 1KB would cost you a lot.

Comment 8

[Marina Rodríguez [:mai]]

On Bug 913552, the data usage graph scren was reviewing by UX, (including the graph scale).
Closed as Works for me.

Comment 9

[Salvador de la Puente González [:salva]]

We don't meet the specification here but let's reopen this if the UX team thinks the exposed behaviour in CC is suboptimal.

Comment 10

[Salvador de la Puente González [:salva]]

We don't meet the specification here but let's reopen this if the UX team thinks the exposed behaviour in CC is suboptimal.