What is the best way to share automated updates to stakeholders that do not have a Software license?

Question

Hey there,

I’m reaching out to discuss a common theme within my organization. Due to licensing constraints, my stakeholders are unable to access our Jira Software project and that essentially eliminates sharing automated updates with stakeholders for ongoing issues.

While Jira offers robust tools for internal team communication and reporting, extending this functionality to external stakeholders who lack direct access presents a unique set of challenges.

I’m eager to hear from fellow community members about their favorite methods or best practices for addressing this issue. Specifically:

* How do you automate updates for ongoing issues in Jira?
* What tools or integrations do you use to share these updates with stakeholders who do not have direct access to the Jira project?
* Have you encountered any particularly effective strategies or workflows for ensuring stakeholders remain informed and engaged?

Spandan · Answer

Hey Mike, the suggestions above (Slack/Teams automation, pulling
data via webhooks) work well if you already have that
infrastructure set up. If you're looking for something simpler
without building out automation yourself, a read-only shared
link is another common pattern — basically a snapshot view your
stakeholders can open in a browser, no Jira license required.

Full disclosure, I'm the developer behind AlloyForge Studios,
and I built a free app for exactly this called Project Share
Portal for Jira, in case it's useful: https://marketplace.atlassian.com/apps/3149999607/project-share-portal-for-jira?hosting=cloud&tab=overview

Either way, hope you found a setup that worked for your team!

Bill Sheboy · Answer

Hi @Mike Tierney -- Welcome to the Atlassian Community!

IMHO, there are no best practices; only better or worse ones for your particular needs / scenario.  That being noted...

* What problems are your stakeholders trying to solve by having updates?
* What do they need to know to achieve that, and with what frequency, level of detail, and feedback mechanism?  How do you know they actually need those things and are using them?
* What recurring conversations happen with the stakeholders?  Why, and what outcomes are produced?
* What other tooling do you have in place, such as Slack, Microsoft Teams, Confluence, etc.?  What about information management and reporting tools?

Pausing to consider these things may help to decide how to proceed.

For some examples with Jira tooling, I have helped teams where the product champion would have regular intake conversations for new (non-urgent) request management, and other progress was available by "pull", where stakeholders could attend the team's standups or sprint reviews.

Others used automated processes to post updates to Slack, Microsoft Teams, etc.  Often, there were more employees with licenses for those communication tools, eliminating the Atlassian licensing constraints.  And with other automation (such as webhooks or REST API functions), other systems could pull data from Jira for reporting.

For larger scale roll-ups, either purpose-built tools for things like enterprise OKR tools or a free graphical board (e.g., Miro) could be used to show context within a journey or story map.

Depending on your enterprise and stakeholder community size, you may do not want to solve such needs by sending "progress emails" and "reports".  I find having some pull-based sources and conversation often helps with effectiveness.

Kind regards,
Bill