New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 626727 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Add directed graph displaying all blockedon connections when passing a bug id in chromedash

Project Member Reported by benhenry@chromium.org, Jul 8 2016

Issue description

With a bug id and project, e.g. 'chromium', as params, construct a graph of all blocking and blocked on bugs.
 
CL in c#1 landed.  Front end CL:
https://critique.corp.google.com/#review/127142604
Status: Started (was: Assigned)

Comment 4 by benhenry@google.com, Oct 20 2016

Status: Assigned (was: Started)
Ping - please provide an update to your high priority bug. This bug is stale. Is it really P-1?

Comment 6 by benhenry@google.com, Jan 19 2017

Labels: -Pri-1 Pri-2
Owner: ----
Status: Available (was: Assigned)
I gave this up and now have not much time.
Owner: benhenry@chromium.org
Status: Assigned (was: Available)
Would it be too much trouble to send a CL to delete any code you added that was specific to the blocker stuff?  You made a bunch of great enhancements to shared code (thanks!) that we should leave but I'm not going to have time to pick up the blocker stuff anytime soon either, and I'd prefer to avoid leaving dead code floating around if possible.
I isolated my CLs, and IIUC, didn't leave anything specific to the blocker code in there. 
Let's talk, maybe I could just revert my changes?
Status: WontFix (was: Assigned)
I already looked, that change that added that mixed in some other helpful stuff too :|

I will actually just WontFix this and don't worry about it.  There's a bunch of other crap I have to rip out anyhow, I'll just make a note for myself to remove anything just for blockers as I go through that process.

Sign in to add a comment