Mary from Planyway Atlassian Partner

@Matthew Sinclair Thank you for the shoutout! 😊 Glad you found our blog post useful. @Mohit Verma By the way, if you're also looking to track your team's workload and logged time across Jira projects (easy export is available), feel free to check out Planyway. It works with Jira Service Management too, and you can easily…

Hi Alex! From what I see, Planyway might be a good fit here (I work there, so I’m a bit biased 😊). Here’s how Planyway maps to your list: Capacity by team, by person, any time horizon - you can group Workload by team and zoom from days to quarters. You can also expand a team to see each person’s load, and overloaded weeks…

Hi @Kim Wright As many have pointed out, you can get that view in the List tab. However, if your goal is to report on delivery work from Epic down to Sub-task level across multiple Jira projects, you may need a view that combines hierarchy with execution details. If that's the case, you may want to take a look at Planyway…

Hi @Cottam_ Oliver _GS_CITLICS_ I think Epic Milestones might be a better fit for what you’re trying to achieve here. Instead of showing the full Epic duration on the Calendar view, you can use milestones to highlight specific delivery dates or important checkpoints inside an Epic. This is useful for things like release…

Hi @Radhika Vijji Have you tried Planyway? Planyway's Table view lets you browse work items in a structured hierarchy (from Epics down to subtasks) instead of a flat issue list. Since it can display work from multiple Jira projects, it's easier to review initiative progress without jumping between individual boards.…

Hi @Faisal Mehboob , It depends on what you’re trying to achieve with your Jira structure. A growing Jira instance usually needs some balance between keeping work easy to manage and keeping visibility across teams. I’d start by looking at ownership and process rather than the number of projects. If different teams own the…

@Carmine Glad you liked it! It looks like Atlassian pushed the retirement back in response to user feedback.

@Danicuordirose Thanks so much for reading and saving the article! 😊 We’re happy it can help. And feel free to share any questions or feedback, we'd love to hear your experience!

Hi Alexander, In Jira, you could use the standard reports like: * User Workload Report Time Tracking Report However, Atlassian is retiring these reports on July 31, 2026, so they won’t be available going forward. As a future-proof replacement, I highly recommend Planyway. As an alternative, Planyway provides several…

@Rukmini Ponnoli Are your referring to Jira Plans or the capacity plugins? Please clarify.

Hi @Namrata Bhomkar I would keep sprint planning in the Jira Software project and use Jira Service Management purely as the customer-facing intake and communication layer. Sprints are an internal execution mechanism, and exposing names such as “Sprint 14” rarely gives customers a useful expectation. IMHO, a practical setup…

Sounds great! You can also book a call for a demo session with my team here: https://calendly.com/planyway-call/demo

Hi Goran, I think your concern is valid, and I wouldn't separate bugs/support work from your team's normal Jira workflow just to make the roadmap planning work. The issue is that Plans assumes the capacity you give it is available for the work included in the plan. Since you already know that around 20% of the team's time…

Hi Antoaneta, If you’re coming from Azure DevOps, the main adjustment is that Jira separates velocity tracking from capacity planning a bit more. Here's what I recommend: * Use story points on user stories to track team velocity over time. Jira’s Velocity Chart and Sprint Reports are designed for this. * Use time estimates…

Hi Alice, This is a common challenge with distributed teams. For workload planning, it helps to separate working hours/availability from just counting assigned issues. A few things you’ll want to look for: * Individual working schedules (for example, someone working 6h/day instead of 8h) * Different capacity settings per…

Hi Alexander, Jira’s built-in issue linking does allow teams to store dependencies (for example, blocks / is blocked by, relates to, duplicates), but Jira does not provide a strong native dependency visualization experience in standard issue views. Advanced Roadmaps adds dependency mapping on a timeline, but it is…

Thanks @Elena_Elevatic That's true! I've mentioned it as well))

Hello Grzegorz, Planyway uses your existing Jira issues as the foundation for resource planning, so you don’t need to duplicate work or maintain separate plans. Resource-specific settings like working hours, availability, and capacity are configured in Planyway to give you a more accurate view of team workload. Best, Mary

Hi Grzegorz, Advanced Roadmaps does not currently support individual or per-user capacity planning. The feature was intentionally updated to focus solely on team-level and sprint-level capacity. If you need to plan both at the individual and the team level, you can use Planyway alongside Jira. Planyway's Workload view…

Hi Carmine, Unfortunately, Jira Plans doesn't flag individual overallocation. You can extend your setup with Planyway. Its Workload view shows each person's planned work alongside their available capacity, even if they're assigned to work across multiple Jira projects or teams. Capacity is calculated based on each person's…

Hi Tatsiana, You can keep Jira as your source of truth and use Planyway to get a cross-project view. With Planyway, you can connect multiple Jira projects, view all work in one place using Timeline, Table, or Calendar views, track dependencies, monitor workload across teams, and get a high-level delivery overview without…

Someone summoned us? :) Hi Tatsiana, Actually, this is exactly the type of problem we built Planyway to solve. Many teams reach a point where spreadsheets stop scaling for cross-product roadmapping and capacity planning, but they also don’t want to replace Jira or move their execution elsewhere. With Planyway, you can keep…

Hi @Golden Glow Cleaners There isn't a single "best" Jira setup—it really depends on how your teams work. That said, a few practices have consistently worked well for growing organizations: * Organize projects around ownership rather than departments. If multiple teams work toward the same product or outcome, a shared…

@joshua_k_twumasi Hi, Unfortunately, this appears to be an intentional product update rather than an isolated issue on your site. Atlassian recently announced the rollout of a unified Timeline experience for Jira Software Spaces, introducing changes such as support for subtasks, work items outside epics, inline editing,…

Hi @Dulari Vikas Pawar Jira is a great tool for managing and tracking product requirements, although it doesn't provide a dedicated "Product Requirements Document (PRD)" template out of the box. A common approach is to combine Jira issues with Confluence (if available) or structure your work directly in Jira. Here's one…

@Anna Patrizia Molero Hi, A blank screen when trying to log time from an issue usually means the issue time-tracking panel or an app-provided module is failing to load, rather than Jira intentionally blocking time logging. I’d suggest checking the following: * Confirm that Jira time tracking is enabled globally and that…

@Linae Luong In Jira Standard, the native timeline view has limited customization options, so displaying due dates directly on timeline bars in a clear, screenshot-friendly way may not be possible depending on your project setup and the fields available in the view. You can usually open an issue to see its dates, and you…

Hi @Peter Lie As a workaround, I’d recommend trying Planyway for Jira. Planyway allows you to visualize Jira issues on a timeline and table view while keeping the hierarchy, parent-child relationships, dependencies, and scheduling structure much clearer for planning and stakeholder communication. The data can be further…

Hi @Balakumar This template is only available in Atlassian Analytics for Jira Cloud Enterprise (or Jira Service Management/Confluence Enterprise) with the Atlassian Data Lake connected and Jira data included in the All data scope. It isn't available in standard Jira dashboards or on Jira Premium. What you'll see The…

Dear team, Is there a way to join beta testers and see upcoming updates?