We have an ask from several team member to grant licenses to business team members that don't user Jira so they are able to get status updates on issues. There are several reasons I am against the idea of licensing somebody to get status updates.
What are you doing to communicate with unlicensed stakeholders on development issues?
Thanks for any ideas.
Dan
This comes up a lot, and the honest answer is that Jira doesn't have a good native path for it. Your options, roughly:
The gap in all of those is that none produces a living, readable view for someone who isn't a Jira user.
Full disclosure — this is the problem I ended up building for; it's in review on the Marketplace now. ClientLens turns a project into a plain-language status page (status, short summary, what's done/in progress/coming up) that you share as a link; no Jira account for the reader. Happy to answer questions either way — and if licensing them is genuinely affordable, that's still the simplest route.
Hello @Andrey - Guenov Labs
Welcome to the Atlassian community.
If you are going to continue to participate in the community please take a moment to review the Community Guidelines.
https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement
Pay particular attention to the guidance in necroposting and the section about Partners.
Also review the Partner Rules of Engagement.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Trudy,
Thanks for the heads-up — appreciate you flagging it rather than just pulling the post. I went and read through both the Community Guidelines and the Partner Rules of Engagement after your comment.
Two things I want to get right: the thread I replied to was from March 2024, so I understand the necroposting concern — going forward I'll only include a disclosed mention of my product on threads that are actually recent, not archive threads. And I'll get my profile properly set up with the company affiliation and Partner lozenge per the "be transparent and authentic" section rather than just disclosing in the text of the post — that's a fair ask and I should have done it before posting, not after.
Let me know if there's anything else I should square away, and thanks again for pointing me at the right docs instead of just reporting it.
Andrey
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Another method is to use Automation Rules to send emails. There you can directly enter the recipient's email which can belong to an unlicensed user.
The practicality of that solution depends on the specific use cases and anticipated usage, as there are limits to the number of rule executions that are permitted per month.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We are currently well under our usage allotment per month, but I would like to keep it that way. If not modeled correctly I could see this getting out of control fast.
Do you know if we could pull an email address from a multi user picker custom field that contained unlicensed users?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A user picker field is picking up user account records, even if they are unlicensed users, so it should be able to access the emailAddress attribute for the users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Our organization uses the Custom Charts for Jira in Confluence plugin. It allows you to use a macro that behaves very similarly to the Jira Issue Filter macro, but looks a lot nicer. But the best feature is the 'impersonation' option, which allows you to view the information on the Confluence page as if you were a different user (i.e. one who has access to Jira).
If they try to drill into the issues, they get a message that they don't have permission to view the issues, but it allows our stakeholders who have Confluence access to see information that comes from Jira without consuming a Jira license.
I have no affiliation with Custom Charts, but I think both this plugin and the Custom Charts for Jira plugins are must-haves if you want to build out useful reports on a dashboard in Jira or in a Confluence page.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Matt, we have "Reports and Timesheets" here already and it does something similar. We are trying that out with one team to see how well it works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Dan W I'll reference this article where you can enable Anonymous access to Jira Cloud.
I don't do this in my project, but I wanted to share the article I found.
Hope that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Dan Breyen wasn't aware this was possible in Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.