fix(linear): update required fields for linear

[waleedlatif1]

Summary

• update required fields for linear

Type of Change

• Bug fix

Testing

Tested all tools manually

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
docs	Building	Preview	Comment	Nov 20, 2025 5:17am

[greptile-apps]

Greptile Summary

• Updated required field configurations across Linear tools to make certain fields optional (projectId in create_issue, teamId/projectId in read_issues, body in update_comment) and others required (title in create_attachment/update_attachment)
• Enhanced input validation to exclude null and empty string values from GraphQL mutations, preventing invalid data from being sent to Linear API
• Improved error handling across all tools with explicit checks for GraphQL errors and missing data in responses

Confidence Score: 3/5

• This PR is mostly safe but contains one logical error that needs fixing
• The PR successfully improves field validation and error handling across 25 Linear tool files, but archive_project.ts has a bug where it references a GraphQL field that isn't queried
• Pay close attention to apps/sim/tools/linear/archive_project.ts which contains a logic error

Important Files Changed

Filename	Overview
apps/sim/tools/linear/archive_project.ts	Improved error handling but references result.entity?.id which is not in the GraphQL query response
apps/sim/tools/linear/create_issue.ts	Changed projectId from required to optional, improved GraphQL mutation structure and error handling
apps/sim/tools/linear/read_issues.ts	Made teamId and projectId optional filters, updated GraphQL query to support dynamic filtering with improved error handling
apps/sim/blocks/blocks/linear.ts	Added conditional required fields based on operation type for better UX in blocks UI

Sequence Diagram

sequenceDiagram
    participant User
    participant LinearTool
    participant LinearAPI
    
    User->>LinearTool: Call Linear operation (e.g., create_issue)
    LinearTool->>LinearTool: Validate required fields
    LinearTool->>LinearTool: Build input object (exclude null/empty optional fields)
    LinearTool->>LinearAPI: Send GraphQL mutation/query
    LinearAPI-->>LinearTool: Return response with data/errors
    LinearTool->>LinearTool: Check for errors in response
    alt Has errors
        LinearTool-->>User: Return error message
    else Success
        LinearTool->>LinearTool: Extract result data
        LinearTool-->>User: Return formatted output
    end

Loading

[greptile-apps]

_{25 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile
React with 👍 or 👎 to share your feedback on this new summary format}

[greptile-apps]

logic: result.entity?.id will always be undefined since the GraphQL query on line 40-45 doesn't request the entity field. Either add entity { id } to the query or use params.projectId here instead.

Suggested change

	projectId: result.entity?.id || '',
	projectId: params.projectId,

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/sim/tools/linear/archive_project.ts
Line: 77:77

Comment:
**logic:** `result.entity?.id` will always be undefined since the GraphQL query on line 40-45 doesn't request the `entity` field. Either add `entity { id }` to the query or use `params.projectId` here instead.

```suggestion
        projectId: params.projectId,
```

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