Iryna Komarnitska_SaaSJet_ Community Champion

Hi Alexander, Since your timesheets already work well, I’d test alternatives against one real planning scenario: someone splits their week across two projects, then one project slips. Can you see the impact on that person, both teams, and the overall timeline without rebuilding the view? If you’re on Jira Cloud Premium or…

Hi, @Quỳnh Buì Hương I’d start with a simple workflow and make sure each ticket has an owner, a clear priority, and enough information for someone to take the next step. It also helps to review blocked and waiting tickets regularly, so they don’t disappear under newer requests. Jira’s native workflow settings are a good…

Hi @Diferencial TI The native JSM calendar may already cover this, as Mihai mentioned. When both Start date and Due date are filled in, requests should stretch across the days between them. Here’s Atlassian’s setup guide to check the date field configuration. If you also need to understand how much working time requests…

Hi, https://community.atlassian.com/forums/App-Central-articles/Bring-structured-configurable-tables-into-Jira-work-items/ba-p/3284594?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_article&utm_content=topic But this happens with all content that you receive via email notifications, not just this…

Hi there, The issue: If you try to go from notifications to email, the page on the community cannot be found The location: Email notification The visuals: Your setup: Browser - Chrome, OS - macOS Tahoe 26.5.2, Device - Laptop.

Hi @Ryan Joyce , Not within the Capacity view shown in your screenshot. Jira’s individual capacity planning currently uses a weekly grid based on a fixed 40-hour workweek. You can switch between percentages, hours, and days, but there is no native toggle that changes the grid to sprint-level periods. Atlassian documents…

Hi @sonali , Jira’s native Velocity Chart does not let you manually select or hide individual sprints. It displays the most recent completed sprints. The chart is board-specific and only includes work items matching the board’s saved filter. Therefore, the closest native solution is to tighten the board filter or create a…

Hi @Suraj , This is a known Jira limitation, not a permission problem. The Team field used by Plans/Advanced Roadmaps is not supported as an X- or Y-axis in the native Two Dimensional Filter Statistics gadget. Atlassian is tracking the request here: JRACLOUD-87800. The native workaround is to create a supported…

Hi @Aryan Raj Pradhan _Student_ , Issues assigned to you and unassigned issues should be treated as different Assignee values. Since your screenshots show different totals - 70 versus 47 - first check that both views use the same filters and issue scope. You can verify the counts with JQL: * <span>assignee =…

Hi @Grzegorz Kostecki , Advanced Roadmaps provides estimate-based capacity planning, but it is primarily calculated at the team and sprint level. It assumes equal capacity across team members rather than displaying issue estimates by assignee. Atlassian documentation Jira Premium and Enterprise also include Individual…

Hi @Fabricio Riveros , Jira’s native Sprint Report shows incomplete issues for each sprint, but it does not calculate: * the number of carryovers per issue; * issues carried over repeatedly; * carryover percentage or trends across sprints. Automation with a numeric custom field is possible, but it only tracks future events…

Hi @christian_vonahlen , I had that problem too. I just cleared all the cookies from all sites with domains ending in atlassian and claude. I restarted my browser, tried connecting again, and it worked.

Hi @Nathan Parfitt , I’m sorry to hear you’re having trouble with our Time in Status app. Please contact our support team, and we’ll be happy to help resolve it. https://saasjet.atlassian.net/servicedesk/customer/portal/1 

Hi @Rama K Goberu , Great question. This article is specifically about the Sprint Performance Report for Scrum boards, so it’s aimed at spotting workload imbalance inside a sprint — for example, when one assignee quietly becomes the “hidden hero” bottleneck. For JSM, the use case is a bit different, since there’s no sprint…

Hi, @Michael Green Yes, you can use: project = PMO AND issuetype in (Story, Task, "Sub-task") AND sprint in closedSprints() AND status = Done ORDER BY assignee However, based on Atlassian’s JQL documentation, closedSprints() returns items from completed sprints in general, not specifically the most recently closed sprint.…

Hi @Mary Doherty , Jira can show cycle time without any JQL, but there’s an important limitation: Built-in Jira reports can visualize cycle time and let you drill into issues but Jira doesn’t natively give you a simple “table/list of issues + (In Progress → Done) duration” as a first-class report in most setups. Control…

Hi @Ashwin Kurundkar , If you’re open to using a third-party app, you might want to try Time in Status (developed by my team). It helps you generate detailed time-in-status reports for any work item types, so you can see exactly how long issues spend in each workflow step. This makes it easier to spot bottlenecks, compare…

Hi @Agustin Etman , If you’re open to using a third-party app, you can try the Custom Fields feature in Time in Status (developed by my team) to calculate time in status. These custom fields are generated based on your work calendar, so the values are calculated in business days (with non-working hours excluded). You can…

Hi @Martina Schütz , At SaaSJet, we also use the OKR methodology. Here’s how it works: We define the OKRs. We set quantitative Key Results (how we’ll measure success). We link Jira work items to those OKRs—so completing the work moves us closer to achieving the results. From there, we can generate reports based on time in…

Hi @Feraud, Nicolas , If you’re open to using Marketplace apps, you can try Sprint Report, which is part of Time in Status—an app developed by my team at SaaSJet. With it, you can see not only a correct Burndown chart for the active sprint, but also team velocity for completed sprints. We also recently released a new…

Hi @Vando Goncalves _e-Core_ , As far as I know, Atlassian Analytics is still quite limited when it comes to work calendar settings. If you’re open to trying an alternative, I can recommend an app from my team at SaaSJet. Time in Status lets you create custom fields that calculate how long each issue spends in a status, as…

Hi @cvanduyn , Recommended: don’t configure the Scrum board for a workflow you can’t execute yet. Set your current “finish line” as Done (Dev) = Ready for QA Env (rename it to make this explicit). Make it a Done status category and set Resolution on transition so sprint metrics stay clean. Track QA/STG/PROD steps as…

Hi @Urmila Ghosh , As a native Jira feature, you’ve already been advised to use the Activity tab. Unfortunately, that approach is fully manual and has to be checked per issue—there’s no way to generate an overall report. If you’re open to using a third-party app, as a SaaSJet representative I can recommend Time in Status…

Hello @noel_langland !I’m part of the SaaSJet team that develops the Time in Status app, which powers Sprint Report. It looks like your app isn’t updated to the latest version. Please update it, and Sprint Report will be available again—now with two new features: a Burndown chart for active sprints and Sprint metrics…

Hi @Aldrine Abisheck , In Jira, nothing actually “stops” when work item moves between statuses—everything is continuously tracked and stored in the changelog. Time in Status, an add-on my team developed, uses that changelog data to generate reports based on how long work items spend in each status. You can also configure…

Hello, @Deepali Dabholkar ! In general, story points aren’t one of the estimation methods available on your board. There are three options in total: Story Points — best for agile teams that prefer estimating relative effort Issue Count — best for teams whose tasks are roughly the same size Original Time Estimate — best for…

Hi @Jamie Scott , Good question! If you’re open to using a third-party app, I’d recommend trying the Sprint Report in Time in Status, an app my team built. It lets you analyze completed sprints and includes a Team Velocity chart that compares committed vs. completed work for the last seven sprints, along with an average…

Hi @Neha Manchanda , If you’re looking for a practical way to do this inside Jira (without building a whole prompt/agent workflow), you might want to try the Sprint Report in the “Time in Status” app — full disclosure: it was developed by my team at SaaSJet. It’s designed for exactly the kind of sprint analysis you…

Hi @Murali Ganesh Chitrothu , Jira already offers several sprint metrics reports, and those have been recommended above. As an alternative, you might consider the sprint report available in Time in Status by SaaSJet (built by my team). The app includes two one-page sprint report options with the key metrics: Active sprint…