Blogs

Create Jira Issues from Gmail with the New Atlassian AppThis is a big one! Atlassian has released a new Gmail add-on that lets you create Jira issues (or, as Atlassian now calls them, "work items" – a term still causing a bit of a stir!) directly from your email.Here’s how it works:

Welcome to a roundup of the latest updates from the Atlassian ecosystem. This week, we're focusing on Trello, the Atlassian community, and other interesting news.Trello UpdatesTrello is a popular tool for simple task management, distinct from Jira which is better suited for IT software development and service desk. If you're unsure which to use, do some research or reach out for guidance.Several updates are coming soon to Trello:

Let's dive into some of the latest updates and interesting discussions emerging from the Atlassian ecosystem. This week, we've got some fascinating developments across Compass, Trello, agile practices, and even a look into Atlassian's AI advancements.

With the Atlassian Team '25 event making waves in the ecosystem—most notably the announcement that Rovo will be free with all Jira plans—there’s a lot of buzz. But while those updates settle in, let’s shift focus to a critical topic: reporting in Jira.

Jira is a powerful tool that can streamline project management and team collaboration, but its effectiveness depends on how well it is implemented and adopted. Organizations often focus on setting up Jira without necessarily evaluating its impact over time. In this blog, we’ll explore key indicators to measure the success of your Jira deployment.

Jira has long been the go-to platform for agile project management, helping teams plan, track, and deliver work efficiently. But with the rise of Artificial Intelligence (AI), the way we interact with Jira is evolving—making it not just a task manager, but a smart assistant for your entire project lifecycle.Smarter Issue PredictionsProblem: Manually categorizing, prioritizing, and assigning issues can be time-consuming and error-prone.

Jira is a powerful tool, but even experienced teams can fall into bad habits that reduce productivity and cause frustration. Here are the top 10 mistakes we often see—and how to fix them for smoother project management. 1. Overcomplicating WorkflowsMistake: Designing workflows with too many unnecessary steps or conditions.Fix: Keep workflows as simple as possible. Only include statuses that add real value to your process.Graphic: A comparison between a complex vs. simple workflow diagram.

By Ravi Sagar | Tea with the Sparks – Weekly Atlassian InsightsWelcome back to another edition of Tea with the Sparxsys—your weekly dose of insights, opinions, and updates from the Atlassian ecosystem.If you’re new here, I cover the latest happenings around Jira, Confluence, Bitbucket, and more—Let’s dive into the latest highlights! ☕👇

Welcome to another edition of "Tea with the Sparks", your go-to source for updates from the Atlassian ecosystem. Whether you're a Jira admin, a Confluence power user, or just exploring what these tools can do, this week brings some exciting news.Let’s dive in! ☕1. 🖥️ Atlassian Command Line Interface (CLI) – Coming Soon!Atlassian is preparing to launch an official Command Line Interface (CLI), which is exciting for those who love scripting and automation.

Jira is one of the most powerful tools in the world of project management and software development. It enforces structure, enables planning, and helps teams stay aligned with workflows. But is Jira always the best choice?Based on my experience, the answer is: not always.Let me explain.🛠️ Jira Is for Process-Driven WorkJira shines when you need your team to follow processes—when you want governance, traceability, and planning in place. It’s fantastic for: