Replaced view x with open in tool for consistency

[yusufaytas]

No description provided.

[greptile-apps]

Greptile Summary

This PR standardizes external link text across the application from various "View X" labels to a consistent "Open in Tool" label, improving UI consistency and user experience.

Key Changes:

• Updated link text to "Open in Tool" across 9 files (alerts, deployments, incidents, services, teams, tickets, and panel components)
• Moved the alert external link from the description section to the header pills area for better visibility
• Changed deployment.actor to deployment.actor.name in the deployments page

Issues Found:

• One logical error in app/(oss)/deployments/[id]/page.tsx where deployment.actor.name is accessed without proper null checking, which could cause a runtime error if the actor object exists but lacks a name property

Confidence Score: 4/5

• This PR is generally safe to merge with one logical bug that needs fixing
• The changes are straightforward text updates that improve consistency. However, there's a logical error in the deployments page where deployment.actor.name is accessed without proper optional chaining, which could cause runtime errors if the actor object exists but doesn't have a name property. This is a critical issue that should be fixed before merging.
• Pay close attention to app/(oss)/deployments/[id]/page.tsx due to the null access issue

Important Files Changed

Filename	Overview
app/(oss)/alerts/[id]/page.tsx	Moved "Open in Tool" link from description section to header pills for better visibility
app/(oss)/deployments/[id]/page.tsx	Updated button text to "Open in Tool" and changed actor to actor.name (potential null access issue)

Sequence Diagram

sequenceDiagram
    participant User
    participant Browser
    participant DetailPage
    participant ExternalTool
    
    User->>Browser: Navigate to entity detail page
    Browser->>DetailPage: Load page (alert/deployment/incident/etc)
    DetailPage->>DetailPage: Render header with pills
    DetailPage->>DetailPage: Check if entity.url exists
    alt URL exists
        DetailPage->>Browser: Display "Open in Tool" link
        User->>Browser: Click "Open in Tool"
        Browser->>ExternalTool: Open entity.url in new tab
    else No URL
        DetailPage->>Browser: Hide link (no action available)
    end

Loading

[greptile-apps]

_{9 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

logic: Accessing deployment.actor.name without optional chaining could cause error if actor object exists but doesn't have name property. Since actor is typed as Record<string, unknown>, the name property isn't guaranteed.

Suggested change

	{deployment?.actor && <Pill label={`by ${deployment.actor.name}`} />}
	{deployment?.actor?.name && <Pill label={`by ${deployment.actor.name}`} />}

Prompt To Fix With AI

This is a comment left during a code review.
Path: app/(oss)/deployments/[id]/page.tsx
Line: 132:132

Comment:
**logic:** Accessing `deployment.actor.name` without optional chaining could cause error if `actor` object exists but doesn't have `name` property. Since `actor` is typed as `Record<string, unknown>`, the `name` property isn't guaranteed.

```suggestion
          {deployment?.actor?.name && <Pill label={`by ${deployment.actor.name}`} />}
```

How can I resolve this? If you propose a fix, please make it concise.