Alina Chyzh_Grandia Solutions Atlassian Partner

Unfortunately, Jira's native Control Chart doesn't allow filtering by specific issue types, and the built-in Cycle Time report only provides the line graph view you mentioned, not a single average number like Azure DevOps shows. You could manually export the data and calculate it in a spreadsheet, but there's no…

Hi! Jira doesn't have a native way to view time logged against an Epic or Story broken down by month. What you can do natively: Jira does record individual worklogs when team members click "Log time" on an issue. You can query those with JQL: project = "YOUR_PROJECT" AND issueType in (Epic, Story) AND worklogDate >=…

Hi @Caryn Yeoh , Jira doesn't offer a built-in single-page view that consolidates multiple projects into one unified dashboard, though you could create a dashboard with multiple gadgets filtered by project or use a saved filter with JQL like "project in (PROJ1, PROJ2, PROJ3, PROJ4, PROJ5)" to see issues across all five…

Hi @Philip Shramko If you're looking to automate this workflow, Automation Action Bundle for Jira can help. I work for the company that built this app. It adds custom actions to Jira's native automation engine, including "Add Users to Groups" and "Remove Users from Groups" actions that let you automatically manage group…

This is a common gap in Jira's native reporting. Native JQL workaround You can't query an Epic's sprint history directly, but you can query its child stories: <span>issueType = Story AND "Epic Link" = EPIC-123 ORDER BY sprint ASC</span> Switch to list view, add the Sprint column, you'll see which sprints each story…

Hi, @chris_walton Unfortunately, there isn't a native way to rank an issue to the top of the backlog using Jira Automation alone. The automation engine can create issues and transition them, but doesn't include a built-in action to change their rank position on the board. If you'd like to automate this, our team built…

Hello, @ehr Currently, native Jira Automation doesn't include built-in actions to calculate relative dates like "next Monday" or to activate sprints directly. If you're looking to fully automate the sprint lifecycle, our app Automation Action Bundle for Jira extends the native automation engine with additional actions…

Hi, @Utsav Kothari The native Jira widgets have limitations when displaying custom field statistics, which is why you're not seeing Story Points as an option in the Two Dimensional Filter Statistics widget. For a native approach, the Filter Results widget can show Story Points but won't aggregate them by assignee in the…

Hi, @Anas Gueroihi Unfortunately, Jira doesn't have a built-in way to automatically assign users to groups based on their email domain when they're added to your instance. The native group membership process is manual, so you'd typically need to go through Users and manually add each person to either your Internal or…

Jira doesn't currently have a single unified timesheet view in its native interface, so you're right that tracking work across multiple tickets can feel scattered. The worklogs are stored per issue, which means you typically need to either open each ticket individually or use a gadget on a dashboard to see your logged time…

Hi, @Sandhya N Unfortunately, Jira's native Epic Burndown report isn't available as a dashboard gadget, which limits your ability to create that configurable dashboard view you're looking for. The built-in dashboard gadgets typically focus on sprint-level burndowns rather than Epic-specific ones. One way to work around…

Hi, @Chris Berry The sprint start and end times you set are primarily used for planning and reporting purposes rather than enforcement. When you manually start a sprint at a different time than scheduled, Jira doesn't prevent you from doing so, and your sprint will simply begin at the actual time you clicked start. The…

This is a classic resource capacity planning challenge. When workload varies significantly by task complexity rather than ticket count, you need a view that factors in time estimates, not just issue counts. Native Jira doesn't offer a built-in capacity planning view that combines assignee workload with estimated time in a…

Thank you! Edited

The Created vs Resolved report in Report Hub (https://marketplace.atlassian.com/apps/1231654/report-hub-custom-charts-reports-timesheets-for-jira - created by our team) is designed specifically for tracking the delta between issue creation and resolution over time, and you can configure it to display data monthly or…

Hi @Nazma Batool Welcome to Atlassian Community! 

Hi @Abhinav,The Jira Timesheet report is mainly focused on logged work, so it won’t directly show you the number of epics or bugs. For that type of breakdown, you’ll need a report that can group and count issues by issue type.One option is using a Card Report (available in Report Hub - Custom Charts, Reports & Timesheets…

Hi @Abhinav,The Jira Timesheet report is mainly focused on logged work, so it won’t directly show you the number of epics or bugs. For that type of breakdown, you’ll need a report that can group and count issues by issue type.One option is using a Card Report (available in Report Hub - Custom Charts, Reports & Timesheets…

Hi @Abhinav, The Jira Timesheet report is mainly focused on logged work, so it won’t directly show you the number of epics or bugs. For that type of breakdown, you’ll need a report that can group and count issues by issue type.One option is using a Card Report (available in Report Hub - Custom Charts, Reports & Timesheets…

The Jira Timesheet report is mainly focused on logged work, so it won’t directly show you the number of epics or bugs. For that type of breakdown, you’ll need a report that can group and count issues by issue type.One option is using a Card Report (available in Report Hub - Custom Charts, Reports & Timesheets for Jira…

Hi @Abhinav, The Jira Timesheet report is mainly focused on logged work, so it won’t directly show you the number of epics or bugs. For that type of breakdown, you’ll need a report that can group and count issues by issue type.One option is using aCard Report(available in Report Hub - Custom Charts, Reports & Timesheets…

Hi @Abhinav, The Jira Timesheet report is mainly focused on logged work, so it won’t directly show you the number of epics or bugs. For that type of breakdown, you’ll need a report that can group and count issues by issue type.One option is using a Card Report (available in Report Hub - Custom Charts, Reports & Timesheets…

Hi, @Jira Admin If you consider Marketplace solutions - you can cover most of this without manual copy/paste using Report Hub’s Roll-up Table Report. It’s built for exactly this kind of management overview. What’s been done so far → The report rolls up work automatically (Epic → Story → Sub-task). Progress bars and…

Hi, @Ramesh Krishnan Jira’s native charts such as Velocity, Burndown and Control Chart are typically limited to board-level or project-level data. That means they don’t support filtering or displaying metrics specifically by Team, especially if your team spans multiple boards or projects. If you're looking for true…

Hi @Jesse Allen Jira doesn’t offer this level of tracking by default. If you’re open to using a Marketplace app, my team developed Report Hub to fill this gap. Planned workload per sprint (per user) is available in the Workload per Sprint report, which you can set up in just a few clicks. What was actually completed is…

Hi @Juan Luis Gil Avalos , If you're open to exploring an app from the Atlassian Marketplace, our team developed Report Hub for Jira Cloud, which provides a straightforward solution. Specifically, the Roll-Up report clearly displays your entire issue hierarchy - including Epics, child issues, and subtasks at all levels -…

Hi @Moheb Hedayat In Jira it’s definitely possible to work with historical data going back to 2018. To do this, you can consider using custom charts available in Report Hub - app developed by our team. It allows you to combine different chart types - bar, line, area, and scatter - to effectively visualize various aspects…

Hello @K Rahul If you're looking for a free solution to track time spent within a specific timeframe, you might want to check out Report Hub, which my team and I developed. With Report Hub's Timesheet you can: Create timesheets filtered by specific date ranges (e.g., only the current week). View logged hours per issue or…

My first suggestion will only work if both projects are in the same Jira instance. If they’re on different instances, JQL alone won’t be able to pull data across them. One way to handle this is by importing data from one instance to another, either using Jira’s external issue import feature or third-party integrations that…

Hi, @Kriti Kashyap You can achieve this in Jira dashboards by using a pre-created filter with the following JQL: Project in (“A”, “B”). Alternatively, you can use Report Hub, an app developed by our team. Report Hub provides: ✅ The ability to apply JQL directly inside reports without needing to create filters beforehand ✅…