Druvis Cukurs (Lineset)

Hi, @Todd Joyce! One more route for the monthly report while ECO-1431 waits, outside MCP. Jira's worklog feed doesn't go through the work item at all, so the 20-entry cap never applies: GET /rest/api/3/worklog/updated?since=<epoch ms> lists the ID of every worklog created or changed since that moment. Start a few days…

in Remote MCP Server: getJiraIssue returns only the oldest 20 worklogs (no pagination or date filter) Comment by Druvis Cukurs (Lineset) October 22

Hi, @Tanvi Sharma! The dashboard gadgets that group work items (Pie Chart, Two Dimensional Filter Statistics) only count them. None of them sums a field like Story Points. Without an app, you can still build an epic-level view for leadership: Add two number fields to your epics, for example "Points done" and "Points…

in How to sum up the story points for leadership reporting and update on dashboard using Story points Comment by Druvis Cukurs (Lineset) October 22

Hi, @Shivoy Malhotra! Picking up your double-counting question, since nobody answered it and it decides which route fits. Natively, Josh's option (2) is the one that holds up: a number field on the epic, and a rule on "Work logged" that goes up to the epic (two Parent branches from a sub-task), looks up its stories and…

in Unable to set up Sub-task to Epic time rollup Comment by Druvis Cukurs (Lineset) October 21

Hi, @Umang dayal! For the percentage itself, the built-in gadgets only count: Two Dimensional Filter Statistics with epics on one axis and status on the other gives each epic's done and total work items, but no %. To get a % column without apps, give epics a number field that an automation rule fills when a child changes…

in Dahsboard to show multiple epic health and progress Comment by Druvis Cukurs (Lineset) October 20

Hi, Kyle! Until the MCP server has a worklog tool, two REST endpoints cover a daily summary: GET /rest/api/3/worklog/updated?since=<start of today, epoch ms> returns the IDs of worklogs created or changed since then, and POST /rest/api/3/worklog/list (body {"ids": [...]}) returns them with author, started, timeSpentSeconds…

in Need to retrieve daily worklog summaries for time tracking and reporting Comment by Druvis Cukurs (Lineset) October 20

Hi, @Andrew Bowie! Your reading of Jira is right: a Task's time total includes its sub-tasks, but the epic's total stops at the Tasks' own logged time. The native fix is automation: a number field on the epic (say "Time spent, all levels") and a rule triggered on "Work logged" that branches to the epic, looks up every work…

in Novice question: how to roll up time tracking in Epic from children's children Comment by Druvis Cukurs (Lineset) October 20

Hi, @Philippe Vignol! Out of the box, the closest is the Two Dimensional Filter Statistics gadget on a dashboard, as Danut said: a filter for your epics' children, epics on one axis and status on the other. It gives you the counts, but no percentage. For an actual % you need a number field on the epic and an automation…

in How to build a jira epic report with % completion based on issues? Comment by Druvis Cukurs (Lineset) October 19

Hi, @Xenia Chilkowich! The Σ Original Estimate field mentioned above only exists on company-managed boards, and only in the card layout, so in a team-managed space the native route really is what you built: a number field on the parent plus an automation rule that sums…

in Why can't I add the aggregated Original Estimate field to an Issue card Comment by Druvis Cukurs (Lineset) October 19

Hi @Barbara Homer, For the "see my time summary" half, natively: save a filter worklogAuthor = currentUser() AND worklogDate >= startOfWeek() and add it to a dashboard as a Filter Results gadget. That's one place listing every issue you logged on this week, a click from each. Its Time Spent column is each issue's total for…

in Is there any way to log all of my work for the week in one place? Comment by Druvis Cukurs (Lineset) October 12

If you keep the two work items, one rule covers both handoffs, because both are a Blocks link: trigger "Work item transitioned" to Done, then "Branch rule / related work items" over the "blocks" links, and inside it comment on each waiting item mentioning its assignee ("Design is done on {{triggerIssue.key}}, ready to…

in Jira processes for engineering and design team integration Comment by Druvis Cukurs (Lineset) October 12

On question 2, natively: worklogDate >= 2026-03-01 AND worklogDate <= 2026-03-31 does catch the ticket that started in January, because it had work logged in March. But the hours shown for it, and in its export, are its total since January. The hours your team logged in March, per ticket, are in each ticket's Work log tab…

in Dashboard and Ticket questions Comment by Druvis Cukurs (Lineset) October 12

To settle the replies above: a sub-task always belongs to its parent's sprint. You can't give it a sprint of its own, and it moves when the story moves. So sub-tasks suit steps that finish in the same sprint as their story (build, test, review). If the pieces need to land in different sprints, make them stories or tasks…

in Is possible to have a sprint field for a sub-task Comment by Druvis Cukurs (Lineset) October 4

For a multi-select, rebuild the whole value each time rather than adding and removing options; that also covers the moved, deleted and archived cases Trudy raised. A scheduled rule (nightly, JQL for the parent type) running per parent: Lookup work items with parent = {{issue.key}}, then Edit work item → More options →…

in Rollup Based on Child Project Tickets Comment by Druvis Cukurs (Lineset) October 4

Since you're going the Automation route, a scheduled rule avoids most of the cascade problems. Trigger: Scheduled, hourly, with "Run a JQL search" set to issuetype = Epic AND statusCategory != Done, so the rule runs once per epic. Action: Lookup work items with parentEpic = {{issue.key}}, which returns the epic, its…

in Time Spent roll-up from Story/Task subtasks to Epic Comment by Druvis Cukurs (Lineset) October 4

Druvis Cukurs (Lineset) Atlassian Partner

Comments