Mary from Planyway Atlassian Partner

Planyway for Jira provides a highly visual and flexible platform that can be configured to meet your reporting needs: * You can typically drill down into an epic to see the individual tasks and the assignees. * As for non-cumulative time, you can easily group the report by tasks as well to see what's needed. * Use…

Hi @jenn Does the problem persist? There was the global issue with Azure servers that affected Planyway. Please let me know if the app still doesn't function.

Let me know if you need help

@Cameron Wong I'm afraid no. There have been many changes since the article was first written. I've updated it today so that it stays relevant. Availability feature can be reached with Planyway.

Hi @Simona Spaccatrosi You've hit on a known limitation: Jira Plans has specific restrictions on which custom field types it can recognize and display. Unfortunately, many custom field types, especially those not native to Jira's core (like some third-party app fields or very complex custom field configurations), are not…

Hi @Simone Griggs One more power-up that offers Repeat feature is Planyway. The app visualizes the card on the calendar as often as you set but doesn't create extra cards on the board.

Hi @Jose Souza You're right that dashboards might not offer the manipulation you're looking for directly within Jira's native functionalities. Many users find themselves in a similar situation when needing to go beyond basic issue counts or simple time aggregates. If you consider using plugins, I'd recommend Planyway for…

@Jon Harry While Jira's native sprint gadgets are project-specific, achieving a multi-project sprint overview is definitely possible, though it often requires a combination of strategies. Enhanced JQL with Filter Results Gadget (for basic metrics): You're on the right track with the Filter Results gadget. While Sprint in…

Hi @karenwendorfheldt What power-up did you use?

@Evgeniya Zemlyanskaya Here is what I think may help: 1. Before declaring victory, we revisit why this Epic existed in the first place. That means pulling in the original Value Hypothesis and Success Metrics custom fields. Example: Hypothesis: By introducing personalized widgets on the dashboard, we believed we could…

@Dan Iwire It's great to hear that the article resonated with you! Your question about teams ingrained in the "folder" mentality is probably the most common hurdle. Here are a few strategies I suppose to be effective: * Don't try to roll this out across every Epic in your entire organization at once. Pick one new,…

@Violetta For cross-cutting work (like platform upgrades, infra changes, shared libraries, etc.), here’s the key: just because the work is technical doesn’t mean it can’t have a value hypothesis. The mistake is thinking: “This supports many things, so it’s not tied to one outcome”. But value can still be defined — it just…

Hi @Aaron Cole If you consider using Trello power-ups, you may try Planyway for Trello. The app has a dedicated view called Timeline grouped by Lists. Each list will have its own lane. That make tracking due dates extremely easy.

Hi @Puru You can explore power-ups for Trello. For example, in Planyway you can connect multiple Trello boards to the same timeline view grouped by people. The view will show you who is doing what and when on the card and checklist item level if needed, plus you'll see all the dependencies to track work easily.

Hi @Billie May As Mile mentioned, the labels do not apply as they are checklists items. If you want to get a clearly distinguished calendar with various label colors, you can try Planyway for Trello. The calendar view is free.

@James Bisset While I understand your frustration regarding the perceived lack of a native reporting facility within Jira, it's important to mention that Atlassian's approach often centers around providing a robust core platform that is highly extensible. This allows users to tailor Jira to their specific needs through a…

@Evgeniya Zemlyanskaya That's a fantastic question and a common challenge, especially in fast-paced environments! It's great to hear the step-by-step guide was helpful. When product goals shift frequently, the key is to build flexibility into your roadmap from the outset and focus on communication and adaptability rather…

Hi @Gary Wells Here is a quick interactive demo. Hope it'll help

Hi @Bernardo Migueis At Planyway we're working on the Jira guide. There are already some videos that might be helpful: General Jira demos: https://planyway.com/blog?platform=demos Time tracking: https://planyway.com/blog/jira-time-tracking-report Capacity planning in Jira: https://planyway.com/blog/jira-capacity-planning…

That's a fantastic and very common question when it comes to capacity planning! It's true that unplanned work like urgent bugs or last-minute requests can significantly impact a sprint, even with the best planning. Here's how you can approach accounting for them in Jira and Planyway: 1. Dedicate a Buffer for Unplanned…

Hi @Asif Khan ! This is a classic challenge with managing complex workflows in Jira, especially when multiple teams and external communication are involved. It sounds like your team is doing a lot of heavy lifting to keep clients updated, and there's definitely room to streamline.General Jira Best Practices &…

Hi @Scott Hassell While Jira itself offers robust capabilities for issue tracking, enhancing it with specialized apps can significantly improve the requirements management workflow. Some of the most popular approaches and apps often focus on: * Dedicated Requirements Management Tools (RMTs) integrated with Jira: These…

As the alternative to Advanced Roadmaps, you can try Planyway for Jira. The app provides flexible roadmapping options and lets you view them grouped by users, teams, components, epics, projects, etc.

Hi @sylvain L While this is a limitation of Jira Plans, you can try Planyway for Jira which is a roadmap with multiple grouping options including components.

@Christopher Hunkele You get extra functionality like workload management, time tracking. Plus, in Planyway there are more roadmap groupings like roadmap by epics, users, projects, teams, components, etc. You also have a chance to visualize your sprints, releases, and milestones. 

Hi @Christopher Hunkele As mentions above, it's all about the subscription you have in Jira. The Basic timeline includes the epic level only. You can trial Jira Plans which is part of Premium. It provides more flexibility. Otherwise there are multiple options on Atlassian Marketplace. Search for roadmap/timeline/Gantt. You…

Hi Afrooz, There's no one-size-fits-all answer, but let's break down some best practices and explore your options. What is the best practice for estimation in Agile teams? The "best" practice often revolves around understanding the purpose of estimation. In Agile, estimation isn't about setting rigid deadlines months in…

Hi @Nina_ASOL You can review this article: how to export in Trello

@Boeing_ Nick A fundamental concept to grasp is that Jira Plans intentionally prioritizes the "Remaining Estimate" over the "Original Estimate" for capacity planning. The "Estimates (h/d)" field within your plan directly corresponds to the "Time remaining" field on a Jira issue. This design choice is geared towards future…

@Elena_Elevatic In essence, a Story focuses on the what and why from a user's perspective, while a Task details the how of the work required. The primary determinant in deciding between a Story and a Task is the concept of user value. A User Story is a description of a feature or functionality from the end-user's point of…