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.

Sign up for GitHub

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

Jump to bottom

In bottom axis of burn-down chart, let's show year only once. #3

Open
kfogel opened this issue May 7, 2018 · 2 comments
Open

In bottom axis of burn-down chart, let's show year only once. #3

kfogel opened this issue May 7, 2018 · 2 comments
Assignees
@kfogel

Comments

@kfogel
Copy link
Member

kfogel commented May 7, 2018

Along the bottom axis of the burn-down chart, let's show the year only once (say at January) instead of repeating it for every month.
@kfogel kfogel assigned PaulMorris and kfogel and unassigned PaulMorris May 7, 2018
@kfogel
Copy link
Member Author

kfogel commented May 10, 2018

Will discuss with @cecilia-donnelly before implementing.

kfogel added a commit that referenced this issue May 10, 2018
@kfogel
WIP: Start on conditional year display (issue #3)
b16de3e
@kfogel
Copy link
Member Author

kfogel commented May 10, 2018

Turns out @cecilia-donnelly agrees about desirability, but it's just harder to implement than we thought.
I've started branch 3-conditionally-show-year to work on it. It's not urgent. In the meantime, I might change to two-digit years on master to at least reduce the visual noise along the X axis.

kfogel added a commit that referenced this issue May 10, 2018
@kfogel
Use two-digit year, as workaround for issue #3
0e247ba
kfogel added a commit that referenced this issue Jun 4, 2018
@kfogel
Use two-digit year, as workaround for issue #3
7c6c5ee
kfogel added a commit that referenced this issue Jun 4, 2018
@kfogel
Cherry pick commit 0e247ba from master
5bdf6b2 
    Use two-digit year, as workaround for issue #3

(This is one of several commits that were cherry-picked from 'master'
to 'reqs-code-here' because the branches had diverged in such a way
that it was easier to adjust 'reqs-code-here' to become the new master
and then merge it with 'git merge --strategy=ours'.)
kfogel added a commit that referenced this issue Jun 4, 2018
@kfogel
Cherry pick commit 0e247ba from master
3e863b1 
    Use two-digit year, as workaround for issue #3

(One of several commits that were cherry-picked from 'master' to
'reqs-code-here' because the branches had diverged in such a way that
it was easier to adjust 'reqs-code-here' to become the new master.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kfogel kfogel

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kfogel @PaulMorris