Skip to main content
AtlassianCustomer feedback

An Atlassian Jira user and developer highlights native limitations where Jira does not roll up story points across subtasks and epics, and subtask logged time fails to aggregate to epics.

Source: Autobound Signal API · 138 signals tracked for Atlassian · updated

Get Atlassian's live signals in Claude or ChatGPT, or by API

AskWhat changed at Atlassian this week? Use Autobound signals for atlassian.com.

What happened

Post: "How to roll up epic story points or time logged in Jira: what Jira does, the free fix, and the app I built"

Source

Post

Highlighted: the lines this signal was extracted from

Hi, r/atlassian! Have you ever encountered the issue that story points don't add up from subtasks to the story or the epic? It was the first problem I ran into when I started using Jira. Here are some ways around it! Disclosure: I'm the creator of the app at the end of this post. The native options come first. What Jira does on its own Time rolls up one level. A story shows its subtasks' time if you tick "Include subtasks", and an epic shows its stories' own time, but time logged on a subtask never reaches the epic (JRACLOUD-70150). Story points don't roll up at all. That request is closed as Not Being Considered (JRACLOUD-90636). The timeline's progress bar counts work items, not points or hours, and only children in the epic's own space. Plans (Premium and Enterprise) rolls estimates up every level, but the totals stay in the plan, not on the epic. The free fix Atlassian has an Automation rule that sums story points into the parent. Point it at a number field of its own so it never overwrites anyone's estimate. It's one level per rule and needs an admin. Team-managed and company-managed spaces also keep story points in different fields, so if your epics span both, you need both. What I built lineset.dev/sumline/ Sumline puts the total on every epic, with a progress bar, and nothing to set up: story points, time spent, original and remaining estimate, added up...

Keep reading with a free account

The rest of this post, and every signal for Atlassian, is in your free account.

Extracted by Autobound

From the Signal API record
Signal
Customer feedback

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/atlassian
Event date
Oct 2026

The full record

From the Signal API record

Numbers

Mentions
11

Details

Timing
Ongoing state
Category
Features
Virality
Very low
Post kind
Multi media
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • story points
  • features
  • work management
  • jira

Products named

  • Jira
  • Jira Plans

Extraction

Sentiment
Negative
Detected
Oct 28, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for Atlassian and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at Atlassian this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/c7b5a470-4daf-5f9d-a3db-e01f829b6be1 returns this record as JSON. POST /v1/companies/enrich returns every signal for atlassian.com.

{
  "signal_id": "c7b5a470-4daf-5f9d-a3db-e01f829b6be1",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-10-28T12:14:55+00:00",
  "company": {
    "name": "Atlassian",
    "domain": "atlassian.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "ongoing_state",
    "topics": [
      "jira",
      "story points",
      "features",
      "work management"
    ],
    "post_id": "1xhmf8m",
    "summary": "An Atlassian Jira user and developer highlights native limitations where Jira does not roll up story points across subtasks and epics, and subtask logged time fails to aggregate to epics.",
    "category": "features",
    "evidence": [
      "[post] Have you ever encountered the issue that story points don't add up from subtasks to the story or the epic? It was the first problem I ran into when I started using Jira.",
      "[post] Story points don't roll up at all. That request is closed as Not Being Considered (JRACLOUD-90636)."
    ],
    "virality": "very_low",
    "post_date": "2026-10-28T12:14:55.000Z",
    "post_kind": "multi_media",
    "post_text": "Hi, r/atlassian! Have you ever encountered the issue that story points don't add up from subtasks to the story or the epic? It was the first problem I ran into when I started using Jira. Here are some ways around it!\n\nDisclosure: I'm the creator of the app at the end of this post. The native options come first.\n\nWhat Jira does on its own\n\nTime rolls up one level. A story shows its subtasks' time if you tick \"Include subtasks\", and an epic shows its stories' own time, but time logged on a subtask never reaches the epic (JRACLOUD-70150).\n\nStory points don't roll up at all. That request is closed as Not Being Considered (JRACLOUD-90636).\n\nThe timeline's progress bar counts work items, not points or hours, and only children in the epic's own space.\n\nPlans (Premium and Enterprise) rolls estimates up every level, but the totals stay in the plan, not on the epic.\n\nThe free fix\n\nAtlassian has an Automation rule that sums story points into the parent. Point it at a number field of its own so it never overwrites anyone's estimate. It's one level per rule and needs an admin. Team-managed and company-managed spaces also keep story points in different fields, so if your epics span both, you need both.\n\nWhat I built\n\nlineset.dev/sumline/\n\nSumline puts the total on every epic, with a progress bar, and nothing to set up: story points, time spent, original and remaining estimate, added up from...",
    "sentiment": "negative",
    "subreddit": "atlassian",
    "event_date": "2026-10",
    "post_title": "How to roll up epic story points or time logged in Jira: what Jira does, the free fix, and the app I built",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/atlassian/comments/1xhmf8m/how_to_roll_up_epic_story_points_or_time_logged/",
    "entity_role": "vendor",
    "post_author": "Lineset",
    "upvote_ratio": 0.6666666666666666,
    "mention_count": 11,
    "mention_surge": true,
    "subreddit_url": "https://www.reddit.com/r/atlassian/",
    "total_upvotes": 1,
    "comments_total": 0,
    "total_comments": 0,
    "post_author_url": "https://www.reddit.com/user/Lineset/",
    "signal_category": "feedback",
    "comments_included": 0,
    "products_mentioned": [
      "Jira",
      "Jira Plans"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.