-
How do you handle client sign-off when the work lives in Jira?
Disclosure: I'm part of the team behind AcceptDeck. For teams delivering work to external clients, I've found there can be an awkward gap between two very different states: The work is done in Jira. and The client has actually accepted it. Internally, everything may be clear. The Jira issue contains the requirements,…
-
Google Fonts for Confluence Update (2026): Runs on Atlassian, 1,942 Fonts, and What's Next
A few weeks ago I wrote 3 Ways to Customize Fonts in Confluence and Which One Actually Works. The short version: native Confluence gives you a small set of system fonts, browser extensions don't work for your teammates, and a Marketplace app — full disclosure, the one I build — was the only way to get real Google Fonts…
-
5 Essential Steps for Salesforce-Jira Integration Success
If your customer support team works in Salesforce while your engineering team works in Jira, you probably don't have an integration problem. You have a context problem. A customer reports an issue. A support agent creates a case in Salesforce. Engineering needs to investigate it in Jira. Product wants visibility into the…
-
Recurring work in Jira: what the built-in recurrence actually does, what it costs you in automation
Disclosure up front: I'm a Marketplace Partner and I build small Jira apps, one of them in this space. Nothing below needs an app and most teams won't need one. I'm writing it because these three things catch people out and none of them are obvious until they've already cost something. Where the built-in recurrence…
-
Before you trust an AI-built Forge app on your Jira site: what grading eleven of them showed
Disclosure: I work at LeanZero, which built this benchmark, and the model results below come from our own runs. In August a member here wrote up their experience of building a WIP limit app for Jira with Rovo Studio, and I've kept thinking about it since. The first version deployed and looked finished, yet in their own…
-
From Schedule Changes to Delivery Risks: Task Slack in Jira
Plans change. A supplier delivers later than expected, a key team member becomes unavailable, testing takes longer, or priorities shift. In a complex Jira project, even a small change can affect dependent tasks, resources, and ultimately the delivery date. The challenge is knowing which tasks have room to move and which…
-
How can different teams stay in sync on one Jira task?
A Jira task can pass through several hands before it's done: it can start in design, move to development, and end in QA. What usually slips is the moment between teams: one step finishes, the next person doesn't realize it's on them, and the ticket sits for a day or two with nobody actively working on it. What helps…
-
Planning work across several Jira projects
Disclosure: I build Ganttry, a Gantt app for Jira, at Plug That App. Most of what follows works with any tool, and I'll say clearly where I'm talking about Ganttry. When a release touches several Jira projects, the plan tends to end up in a spreadsheet, or in a few timelines that nobody keeps in sync. Here's what we've…
-
Before Sync: a short review of public Confluence documentation
I develop Public Pages for Confluence at TypeSwitch. Before one Public Pages update, I edited the documentation directly in Confluence. I updated the text on several pages, clarified headings and descriptions, and adjusted the structure and links between sections. Read it as an external user Before running Sync, I went…
-
6 AI-powered testing tools for Jira
Are your testers still writing test cases like it's 2009? Modern software teams often rely on Jira to manage development and testing workflows. However, as projects grow, testing can become a bottleneck: creating and maintaining test cases takes time, tracking executions is difficult, and critical defects sometimes slip…