Habib__Plugio__ Atlassian Partner

Hi! This is a common pain point — JQL filters don't traverse the issue hierarchy, so a filter on an Epic won't automatically include its stories and subtasks. A few options: * Plain JQL — you can chain it manually: parent in ("EPIC-123") returns the stories, but reaching subtasks means listing story keys by hand, which…

Hi @Radhika Vijji , Full disclosure: I'm the developer of a marketplace app that covers this, but let me start with the native answer since it's genuinely relevant. Native options: What you're describing (the progress panel with drill-down) lives in Plans, which needs Jira Premium — and even there it stays inside the Plans…

Hi @Naveena Tati Disclosure: I'm the developer of this app. This is exactly the gap our Plugio Suite – Dashboard Builder for Jira tries to close. It has a sprint mode: you bind a Jira board, and every widget scopes to the active sprint automatically (rolls over each sprint, or you can pin one). So instead of "created vs…

Hi @Michael Day Addition to previous answer, you can make date filters dynamic like below. status CHANGED DURING (startOfMonth(-1), endOfMonth(-1)) AND statusCategory != "To Do" For visualization, you may want to check out Multi Dimensional Pivot Table gadget. (disclosure: I work on it)

Hi @piyushgupta You can often get a lot of this using Jira's native "Filter Results" and "Created vs. Resolved" charts, especially with some well-crafted JQL. For more advanced visualizations and custom KPIs directly on a dashboard, you might look into apps like Report Cards & Charts for Jira Dashboards (disclosure: I work…

Hi @Carmine Jira Plans doesn't automatically warn about over-allocation in the way you're describing. You'll typically need to manually check the "Capacity" view for each team member and compare their assigned work (story points or hours) against their set capacity for the sprint. If the assigned points/hours exceed their…

Hi @Eric Bailey You can use `sprint in openSprints(), futureSprints()` combined with a JQL filter for the specific team field if you have one. Or, if your sprints are named consistently, you might be able to use a JQL clause like `sprint ~ "Next Sprint - Team*"` to catch all three. Irrelevant from question, our Sprint…

Hi @Balakumar You can often get a good view of this by using JQL to filter by sprint and then grouping by status, or by creating separate gadgets for "Committed" (e.g., in progress or to-do status at sprint start) and "Completed" (e.g., done status at sprint end). Also you can check our widgets for more advanced…

Hi @Ramesh Krishnan Jira can actually do a basic version of this out of the box. On a classic dashboard, add the Two Dimensional Filter Statistics gadget: * Create/save a filter like issuetype = Story AND "Epic Link" is not EMPTY * Add the gadget, point it at that filter * Set the X axis to "Epic Link" and you'll get a…

Hi @PLaksh11 , I think Jira doesn't have ability to create a report like this. If you prefer to use a third party plugin, you may check out our Multi-Dimensional Pivot Table plugin. It has ability to show multiple measures and conditional counting ability described as in your use case and it is completely FREE. -- Habib,…

Hi @Suraj You might be running into issues if the "TEAM" field isn't a standard Jira field or if it's a custom field that hasn't been properly configured for use in dashboards or reports. Sometimes, custom fields need to be associated with specific screens or project configurations to show up in these areas. Also you check…

Hi @Duong Nguyen Hong , That's a common challenge when trying to build precise JQL queries! Unfortunately, native Jira JQL doesn't directly support querying based on the status of a linked issue in the way you've described. The "linkedIssue()" function is primarily for checking the existence of a link or the type of link,…