Guenov Labs

ClientLens for Jira — Docs

Testing ClientLens (quick start)

To see ClientLens end to end in about five minutes:

  1. Install ClientLens into a Jira Cloud site (requires a site admin). New installs get a 30-day free trial, so no subscription is needed to test.
  2. Open any Jira project, select More in the project tab bar, then select ClientLens.
  3. Select New client page, choose "This project" as the source, and select Generate draft.
  4. Set a health verdict (On track / At risk / Blocked), optionally edit the summary, and select Publish.
  5. On the Client pages list, select Copy link (or Open page).
  6. Open that link in a private/incognito browser window — or any browser where you're not logged in to Jira. You'll see the client-facing status page exactly as an external client would: no Jira account or login required.

That final step is the core of the app: a plain-language, no-login status page generated from a Jira project. Everything below explains each part in more detail.

What ClientLens does

ClientLens turns a Jira project into a short, plain-language status page you can send to a client. You choose what to show, set a clear health status, and publish a link — no Jira account or login required on their end. Update the page any time; the link you already sent keeps working and shows the latest content.

Getting started

  1. Install ClientLens from the Atlassian Marketplace into your Jira Cloud site. This step requires a Jira site admin.
  2. Open ClientLens from any Jira project. Select More in the project tab bar, then select ClientLens.
  3. New installs start with a 30-day free trial. After the trial, publishing new or updated pages needs an active subscription — but any client pages you've already published stay live for your clients either way. See "Managing client pages" below.

Creating your first client page

  1. From the ClientLens home screen, select New client page.
  2. Choose a source: this project, a specific board, or a saved filter. Most people use "This project."
  3. Select Generate draft. ClientLens pulls the matching Jira issues and sorts them into three groups: Recently done, In progress, and Coming up.
  4. Name the page. This label is only for you — it's how you tell pages apart in your list, and your client never sees it. It matters once you publish more than one page for the same project (for example, "Acme — CEO view" vs. "Acme — team view").
  5. Review and edit before anything is shared:
    • Every item is editable or removable. Trim or reword anything that shouldn't go to a client — a client's name, an email address, an internal note.
    • Write the summary yourself, or select Generate with AI for an editable draft. Either way, it's yours to edit before publishing.
    • Set the health verdict: On track, At risk, or Blocked.
    • Set the project state: Active, Paused, or Complete.
  6. Add your branding: a display name, an accent color, and an optional logo URL (must be https://).
  7. Check the "Here's what your client will see" preview at the bottom of the page.
  8. Select Publish to get your shareable link.

If a source has 100 or more issues, ClientLens shows only the most recently updated 100 and flags this on both the draft and the published page, so nothing looks like a complete list when it isn't.

After publishing, you're back on the Client pages list, with your page briefly highlighted. From there:

  • Copy link copies the client's link to your clipboard.
  • Open page opens the page exactly as your client will see it.

Because of how Jira sandboxes apps, automatic copying doesn't always work. If it doesn't, a small window opens with the link already selected — press Cmd+A then Cmd+C (Mac) or Ctrl+A then Ctrl+C (Windows/Linux) to copy it. Open page always works, so you can also open the link and copy it from your browser's address bar.

Your client needs no Jira account and no login — just the link.

Updating a page

Open a page's ••• menu, select Edit, make your changes, and select Republish.

The link stays exactly the same. Any link you've already sent keeps working and now shows the updated content — you don't need to send a new one.

Managing client pages

The Client pages list shows every page for the project: its name, health verdict, project state, source (project, board, or filter), and when it was last published.

Each page's ••• menu has:

  • Edit — reopen the page to change its content, verdict, or branding.
  • Replace link — immediately retires the current link and creates a new one. Use this if a link leaked or went to the wrong person; anyone with the old link sees an "access denied" page.
  • Disable link — turns the link off without deleting the page. The page's content stays saved, so you can bring it back later with Generate new link.
  • Delete page — permanently removes the page's content and link. This can't be undone.

You can publish more than one page for the same project — give them distinct names so you can tell them apart in the list.

Page states

  • Active — your client sees the health verdict you set: On track, At risk, or Blocked. Each status is always shown as a color, an icon, and a word together, never color alone.
  • Paused — the client sees a neutral "Project paused" banner instead of the verdict.
  • Complete — the client sees a "Project complete" banner instead of the verdict.
  • Just getting started — if there's nothing in any group yet, the client sees a neutral banner instead of a verdict, so an empty page never reads as bad news.

Whatever's in Recently done, In progress, and Coming up still shows beneath the banner in every state, as long as there's something in it.

Branding

  • Logo URL must be a direct link to an image starting with https://. ClientLens won't display a logo from any other kind of URL.
  • Accent color styles the page's header only — the thin rule under your logo and name. It never changes the status color. On track, At risk, and Blocked always use the same fixed green, amber, and red, so the health signal reads the same no matter whose brand is applied.

Privacy and security

Your Jira data stays on Atlassian's infrastructure. AI summaries are drafted using Atlassian's own on-platform AI — nothing is sent to an external AI provider. Client pages are read-only: there's nothing on them your client can edit. Each page's link can be replaced or disabled independently, without affecting any other page.

For full details, see the Privacy Policy and the Trust Center.

Troubleshooting / FAQ

  • My client says the link doesn't work. Open the Client pages list and check whether that link was replaced, disabled, or the page was deleted. If you replaced the link, make sure you sent the client the new one — the old one stops working immediately.
  • Can my client edit anything? No. The page your client sees is read-only.
  • Do I need a Jira license for my client? No. They don't need a Jira account, a license, or a login of any kind — just the link.
  • Why isn't my logo showing? The logo URL must be a valid, direct https:// link to an image. Links that aren't https://, or that don't load, are skipped silently rather than shown broken.
  • What happens to my pages if I uninstall ClientLens? Uninstalling permanently deletes everything ClientLens stored for your site — every page's content and every link. None of it is recoverable afterward.
  • Can I use a board or filter, not just a project? Yes. When creating a page, choose a board or a saved filter as the source instead of the whole project.

Support

Reach us at support@guenov.dev. We reply within 1–2 business days, Monday–Friday. See our full Support SLA for details.