Kitawolf Studios
  • Home
  • WordPress Plugins ▼
    • Kitawolf Unregistered Tag Cleanup
    • Kitawolf Dead Links Checker
  • Atlassian Apps ▼
    • Parent Pulse for Jira
    • Sprint Subtask Pulse for Jira
  • Web Apps ▼
    • LevyTrack
  • What We Do
  • Custom Solutions
  • Contact
Start a Project

Parent Pulse for Jira

Parent Pulse user guide

About Parent PulseUser guideSupportSecurityPrivacyTerms

What Parent Pulse does

Parent Pulse adds a read-only panel to Jira parent work items. It calculates a live rollup of the direct children the current user is allowed to see.

The panel shows:

  • Completion percentage
  • Done, in-progress, and to-do child counts
  • Total time logged
  • Total remaining estimate
  • How many children have time estimates

Install and open the panel

Parent Pulse is being prepared for Atlassian Marketplace. Once the listing is available:

  1. Ask a Jira site administrator to install Parent Pulse: Progress Rollups for Jira from Atlassian Marketplace.
  2. Open a parent work item with direct children, such as an Epic.
  3. Open the work item's app actions.
  4. Select Parent Pulse.

Jira remembers the panel on that work item. Select Refresh after changing child statuses or time-tracking values.

How calculations work

Completion

Completion is the number of visible direct children in Jira's Done status category divided by the total number of visible direct children. Parent Pulse uses status categories rather than English status names, so custom workflows remain compatible.

Status counts

Every visible direct child is grouped into Jira's To Do, In Progress, or Done status category.

Time

Logged time is the sum of Jira's time-spent values. Remaining time is the sum of Jira's remaining-estimate values. Durations are shown as accumulated hours and minutes, without assuming a site's working-day length.

Estimate coverage

A child counts as estimated when its original or remaining time estimate is greater than zero. Logged time alone does not count as an estimate. Parent Pulse reports the count explicitly so missing estimates are not silently treated as complete estimates of zero.

Permissions and restricted children

Parent Pulse calls Jira as the signed-in user. A child the user cannot browse is not exposed and is not included in that user's totals. Two users can therefore see different totals on the same parent when Jira permissions or issue security differ.

Current product boundaries

  • Direct children only; no recursive multi-level hierarchy
  • Jira time tracking, not story points
  • Read-only; Parent Pulse does not edit work items or estimates
  • Live issue-panel rollup; no JQL-searchable stored rollup field
  • Jira Cloud only

Troubleshooting

No child work items

Confirm that the current work item has direct children and that you have permission to browse them.

Totals do not match another user

Check Jira browse permissions and issue-security restrictions. Parent Pulse intentionally respects each user's visibility.

Time values are missing

Confirm Jira time tracking is enabled and that the children have original estimates, remaining estimates, or logged time.

The panel reports an error

Select Try again or Refresh. If the problem continues, contact support@kitawolfstudios.com with the Jira site URL, parent key, approximate time, and visible error text. Do not send confidential issue content.

Kitawolf Studios

Engineering premium plugins, beautiful applications, and memorable games tailored to your exact specifications.

Navigation

  • LevyTrack
  • Home
  • Parent Pulse
  • Sprint Subtask Pulse
  • Contact

Support & Inquiries

Have questions? Get in touch:

Contact Support Form

© 2026 Kitawolf Studios. All rights reserved.

Privacy PolicyTerms of Service