Jira

1) Scale agile planning beyond individual teams Jira enabled planning across epics, initiatives, and multiple teams, allowing leadership to understand progress, dependencies, and risks at the program and portfolio levels. 2) Strong visibility and transparency The platform provides a shared system of record for work, enabling consistent reporting, status tracking, and governance across IT, business, and external partners. 3) Flexible planning model adaptable to entre^rise realities Jira supports hybrid approaches (Agile, Scrum, Kanban, and waterfall-like milestones), which is critical for large entreprise programs where not all work fits a pure agile model 4) Ecosystem and extensibility Capabilities can be extended through Advanced Roadmap, plugins, automation, and integrations with Confluence, reporting tools, and financial trsacking solutions

Integrating with Bitbucket, Confluence and other first-party Atlassian products works really well.

I appreciate how Jira supports our complex manufacturing operations through powerful agile planning and tracking capabilities. The combination of powerful scrum and kanban boards makes it easy for me and my team to visualize workflows, manage backlogs, run sprints and track tasks, enabling everyone to stay aligned with project goals. Jira's comprehensive reporting and real time insights help us monitor project progress, spot inefficiencies early and make data driven decisions to keep production on schedule. Its collaboration tools enable all our department, from production to sales to stay connected and informed at all times. I especially love the customizable dashboards, which give us clear overview of production line performance and help us quickly identify and resolve bottlenecks.

1) Entreprise planning capabilities are not fully native out of the box Advanced portfolio planning, capacity forecasting, and cross-program dependency management often require add-ons (e.g. Advanced roadmap, Tempo) or custom configurations 2) Reporting and executive visibility require extra effort Leadership-level reporting is powerful but not turnkey. Consistent portfolio reporting usually depends on plugins, custom dashboards, or external BI tools 3) Governance relies heavily on discipline, not enforcement Jira's flexibility is a strength, but without strong governance (naming conventions, issue hierarchy, workflows, enterprise usage can quickly become inconsistent 4) Learning curve when scaling beyond team usage Jira is easy to adopt at team level, but scaling it to enterprise agile planning requires experienced configuration and process ownership

The UI changes recently have been kind of weird for our use case, the new description editor works pretty well, but it's still annoying to find and link other tickets. Perhaps this is because of the way we are using/abusing the system though. And sometimes it does not pull in MR details from our Gitlab repositories.

Despite its powerful project tracking features, Jira lacks built-in portfolio management tools, making it harder to manage multiple projects across different production lines. Additionally it doesn't offer a robust budget tracking features to monitor project costs and hours worked, which limit our ability to keep expenses under control. Lastly, jira's wide range of features makes deployment complex and causes a steep learning curve that slows down its adoption and makes it hard to fully utilize its capabilities in our manufacturing operations