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

Triage Dashboard - if untriaged issues > 50, mark the number as red for alert #1950

Closed
MDTsai opened this issue Dec 1, 2017 · 3 comments
Closed

Triage Dashboard - if untriaged issues > 50, mark the number as red for alert #1950

MDTsai opened this issue Dec 1, 2017 · 3 comments
Labels
scope: dashboard type: feature request
Milestone
January / Februar...

Comments

@MDTsai
Copy link
Contributor

MDTsai commented Dec 1, 2017

Easily to know if there is issue flood from sprint?
@karlcow karlcow added this to the NeedsTriage Issues Dashboard - Phase 2 milestone Dec 4, 2017
@karlcow
Copy link
Member

karlcow commented Jan 4, 2018 •
edited
Loading

@magsout What do you think? Should we send something from the server side, alert: True if it's becoming more than 50. Or should we just handled the color on the client through JS. aka if the number is 50, background-color: red

@karlcow karlcow modified the milestones: NeedsTriage Issues Dashboard - Phase 2, January / February / March 2018 Jan 9, 2018
@magsout
Copy link
Member

magsout commented Jan 11, 2018

@karlcow I think that solution number 2 is good

@karlcow
Copy link
Member

karlcow commented Jan 11, 2018

ok let's do that. :) Thanks @magsout

magsout added a commit that referenced this issue Jan 11, 2018
@magsout
Issue #1950 - changed style if untriaged issues > 50
02037ed
magsout added a commit that referenced this issue Jan 12, 2018
@magsout
Issue #1950 - changed style if untriaged issues > 50
760e3dc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
scope: dashboard type: feature request
Projects
None yet
Milestone
January / February / March 2018
Development

No branches or pull requests
4 participants
@karlcow @zoepage @magsout @MDTsai