Feature: Add estimate support to issues

[g-click-trade]

Issue co-written with dear assistant Claude Code 🤖

Feature Request

Add support for reading and setting estimates (story points) on issues.

Current Behavior

linearis issues read does not return the estimate field, and there's no way to set estimates via CLI.

linearis issues read TES-123 | jq 'keys'
# Returns: branchName, comments, createdAt, description, embeds, id, 
#          identifier, labels, priority, state, subIssues, team, title, updatedAt
# Missing: estimate

Proposed Solution

1. Read: Include estimate field in issues read output
2. Create: Add --estimate <number> option to issues create
3. Update: Add --estimate <number> option to issues update

Example Usage

# Create with estimate
linearis issues create "New feature" --team ENG --estimate 5

# Update estimate
linearis issues update ENG-123 --estimate 8

# Read estimate
linearis issues read ENG-123 | jq '.estimate'

Context

Linear supports multiple estimation scales per team:

Scale	Values
Fibonacci	0, 1, 2, 3, 5, 8, 13, 21
Exponential	0, 1, 2, 4, 8, 16, 32

[g-click-trade]

Workaround available: https://gist.github.com/g-click-trade/3d73f0492abd2e5c75baa863053867dc

# Download and use
curl -O https://gist.githubusercontent.com/g-click-trade/3d73f0492abd2e5c75baa863053867dc/raw/linearis_workarounds.py

# Get estimate
python linearis_workarounds.py estimate get ENG-123

# Set estimate
python linearis_workarounds.py estimate set ENG-123 5

[iamfj]

#41

[iamfj]

Hi @g-click-trade — first of all, thank you for opening this and for supporting Linearis with thoughtful feature requests like this.

I took another careful look, and I believe this is now addressed in the current codebase. Sorry it took us this long to circle back properly on the issue.

Community input like yours genuinely matters to us. We want to honor the people who take the time to report gaps, suggest improvements, and help make the tool better for everyone. Thank you for that.

What’s included

Estimate support is now available for issues:

• issues read includes the estimate field
• issues create supports --estimate <n>
• issues update supports --estimate <n>
• issues update also supports --clear-estimate

Examples

# Read an estimate
linearis issues read ENG-123 | jq .estimate

# Create an issue with an estimate
linearis issues create "New feature" --team ENG --estimate 5

# Update an issue estimate
linearis issues update ENG-123 --estimate 8

# Clear an issue estimate
linearis issues update ENG-123 --clear-estimate

Where this was shipped

This was included in v2026.4.3:
https://github.com/linearis-oss/linearis/releases/tag/v2026.4.3

And it was implemented in PR #94:

If you’re okay with it, I’d close this issue as addressed. And if you notice anything missing or behaving differently than expected, please feel free to reply here — we’d be happy to take another look.

Thanks again for helping improve Linearis 💛