Tag
Jira has no dedicated 'export to PDF' button for issue lists, but you can produce a PDF for free using your browser's print-to-PDF function on a filtered issue view, or by exporting a single issue's printable view. The output quality depends almost entirely on how few columns you include and whether you print in landscape. Marketplace apps are worth it only if you need templates, branding, or scheduled generation.
When a Jira automation rule doesn't run, check the rule's audit log first — it tells you whether the rule fired at all, fired and was filtered out by a condition, or failed with an error. From there the usual causes are: the rule is disabled, its scope is wrong, the trigger doesn't match, a condition is filtering everything, the actor lacks permission, or you've hit your plan's execution limit.
A scheduled Jira automation that sends one email per issue is almost always caused by putting JQL in the scheduled trigger itself. When the trigger matches issues directly, the rule runs once per matched issue. Move the JQL into a Lookup Issues action, leave the trigger's JQL empty, and loop over the results in a single email.
A Jira link only works for someone with an Atlassian account, access to your site, and browse permission on that project. External people have none of those by default, so they hit a login wall or a 'you don't have permission' error. The options are to license them, use guest access on a paid plan, or send the information rather than the link.
If everyone in your company can see your Jira project, it's almost always because the Browse Projects permission is granted to 'Any logged-in user' in the project's permission scheme. That default makes the project visible to every licensed user in your site. Change that grant to a specific project role or group and the exposure stops.
You can build a genuinely good client status dashboard in Confluence using Jira macros — a summary, live issue lists, and a roadmap, all updating from your real data. The catch that decides everything: your client still needs Confluence access to see it, unless you publish the page publicly. Here's the full build, and how to tell if it's the right route for you before you invest the afternoon.
A Jira permission scheme is just a reusable list of 'who can do what,' attached to one or more projects. Most permission confusion traces to a single setting — the Browse Projects permission granted to 'Any logged-in user' — which quietly lets everyone in your instance see a project. Understand roles vs groups, fix that one default, and permission schemes stop being scary.
Jira is built for internal teams, not client-facing work, so agencies adopt it for delivery and then hit a wall: no clean, cheap way to show a client how the project is going. Everyone builds the same patchwork — PDFs, spreadsheets, extra meetings, licensed seats — and the cost compounds per client. Here are the honest options, including when a full-access tool beats a status-page tool, and vice versa.
Atlassian built Atlas specifically to keep non-technical stakeholders in the loop on project status — and the fact that they built it proves the need is real. Over 2025 they folded Atlas into Atlassian Home, and left genuine confusion (disputed even by their own staff) about whether unlicensed stakeholders can still follow projects. That confusion is the whole problem in miniature. Here's what teams are using to fill the gap now.
External Share for Jira gives external users the real Jira board. ClientLens gives them a plain-language status page with no board at all. They look like competitors but solve opposite problems: one is for collaborators who need to work in the project, the other is for readers who just need to know if it's on track. Pick by asking which one your person is.
You can send a scheduled weekly summary email from Jira using a native Automation rule — no apps required. The trick most people miss: put your JQL in a Lookup Issues action, NOT in the scheduled trigger, or you'll get one email per issue instead of one summary. Here's the full setup, with the smart-value syntax for a clean issue list.
Jira Cloud has no guest role. Every account that can see a project consumes a licensed seat, with one narrow exception (the Jira Service Management customer portal). Everything else people call 'guest access' is one of three workarounds: automation emails, anonymous public access, or a sharing app. Which you want depends on whether your guest needs to work in the project or just see it.
The weekly PDF export feels free because you pay for it in time, not money — and time costs are easy to stop counting. But it's stale on arrival, it makes you the bottleneck for every question, and the cost scales linearly with every client you add. The fix isn't a specific tool — it's shifting from an artifact you produce to a view your client consults.
There are six ways to show a client Jira status without a license: license them anyway, automation emails, anonymous access, Confluence, manual exports, or a sharing app. Most fail — not because access is hard, but because access was never the problem. Your client doesn't want to see Jira. They want to know if the project is okay.
ClientLens for Jira
