Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability To Set y-Axis Start Point #4

Open
jakejgordon opened this issue Aug 15, 2014 · 4 comments
Open

Ability To Set y-Axis Start Point #4

jakejgordon opened this issue Aug 15, 2014 · 4 comments
Assignees

Comments

@jakejgordon
Copy link

As a user with a long running project, I can set a y-axis start point so that as the number of completed points over time gets large I can still make sense of the smaller bands (like In Progress or In Testing).

See attached image for an example of where this would be useful. Over time, one of the bands has a tendency to get very large and squeeze out all of the other bands. If we could adjust the graph to start at 500 points (in this example) instead of 0 then we could see the details of the other bands more easily.

cumulative_flow_y_axis

Thanks again, I love your tool!

@jakejgordon
Copy link
Author

To clarify, the reason that I don't just exclude the Kanban State of "Production" is that you want to see that band growing to represent what is getting deployed to production.

@jmartin-rally jmartin-rally self-assigned this Aug 26, 2014
@jmartin-rally
Copy link
Contributor

Before I go too deep into this one, have you tried the zoom? If you highlight from what you want the starting point to the top and over to the right in a single drag, you'll make a rectangle that will set the zoom, which seems to do what you want. We just don't save the setting.

@jakejgordon
Copy link
Author

Zooming definitely helps but since it doesn't save the last zoom setting you have to do it every time. And if you have a large band on top (e.g. backlog) and a large band on the bottom (e.g. completed) then when you zoom in on the narrow band that you care about (e.g. in progress, testing, user acceptance) you still can't see the total numbers for the top band unless you capture the top of that band -- which defeats the purpose of zooming in the first place.... if that makes sense.

Another option rather than explicitly picking the starting y value would be an option to make the y value offset by the value of y at x = 0. In other words, if your "completed" band at the bottom started at 575 at x = 0 and grew to 700 over 30 days, then your starting y value would be 575 and you could easily see the growth from 575 to 700. I realize this is a tough one from a UX perspective in terms of how you present that setting. If you figure out a way to solve this then you are a genius. :)

@jmartin-rally
Copy link
Contributor

Thanks, that makes it clearer. I'm having trouble because much of my data is by default coming out as lots of small areas on the bottom so starting at y=100 eliminates those areas. I suppose I'll want to put a setting for arranging the data stacked by size instead of by order. I'll noodle on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants