Michael Neale added a comment - 2017-05-30 00:18 For cliff to investigate. I am not sure if this has aything to do with react, more just URI elements -> highlighted top element. 

Cliff Meyers added a comment - 2017-05-30 19:53 - edited cc sophistifunk on this one, maybe we can devise a solution here. Current mechanism for tab selection on Run Details is using TabLink, which internally uses router.isActive, and the route path matches exactly. route.isActive will also return true if the path matches a parent Route. For example, if current route path is '/organizations/jenkins/artifacts-150/activity': router.isActive( '/' ) // returns true , as the this the top level route definition that matches everything router.isActive( '/organizations/jenkins' ) // returns true , since we define a route with path= "organizations/:organization" router.isActive( '/organizations/jenkin' ) // returns false , since the organization path var doesn't match router.isActive( '/organizations/jenkins/artifacts-150' ) // returns false , since that isn't actually a Route, but rather a Redirect that pushes the user to the /activity child route router.isActive( '/organizations/jenkins/artifacts-150/activity' ) // returns true , exact match So technically this could be made to work if the top-level Link was a TabLink and its "to" prop pointed at a route path that was the parent for all other route. To make "Pipelines" do this would be harder (impossible?) since the route structure has a few different top-level routes (below "/" anyways) and using "/" would leave it active for all routes I think. sophistifunk does that sound right to you? If we can confirm the current pieces can't be made to work in a reasonable fashion, I may have an alternative idea or two.

Josh McDonald added a comment - 2017-05-30 21:14 Yes, that makes sense. There's probably a way to query the router and get the link that `/` would redirect to, though? Then we could use that for the "Pipelines" tab url maybe?