[!] Sharepoint: File access in Jira
Confluence Seite Permissions anpassen >> “share” >> open
We’re still optimizing our files feature!
Detailed information and updates will soon be available. Stay tuned 🚀
Based on: File Feature Exploration
Run the automation to be informed about any new e.g. epic being created in your space
Use one shared Teams chat per Epic to keep all development communication in one place.
Every child work item automatically syncs with the same chat, providing full transparency.
Configure epic chat automations to your individual needs. Set-up different e.g. epic chat automations for your Jira space to align with the different needs and purposes of projects and participants.
Releases affect multiple stakeholders such as developers, product managers, marketing, and support. Use one Teams channel to keep everyone aligned on what has been released and what remains open.
Post release updates in a dedicated Teams channel to share the latest information and inform the team, if related work items still require attention.
Requirements
Steps you should take before setting up the project automation in your Jira space:
Service User: Set-up a service user to be used for the automation >> Link DOKU
Template: Define a text template as the basis for the initial message. Also required to be chosen from the drop down menu when configuring the Preset for the epic chat. (see below)
Preset: Set-up an [Issue Type] Preset before, in order to run relevant actions after posting the Teams chat. Only configured built-in automations will be relevant here.
Feature at a glance
Simplified release communication: Post release updates directly to Teams channels, so development, product, and support teams have a single view of what has shipped.
Release channel in Teams: Automatically post release updates to a shared Teams channel when a release is completed in Jira. Include key details such as linked Epics, resolved work items, and open bugs.
Release notifications: Use adaptive cards to summarize each release. Include the release name, associated Epics, and next steps. Notifications can tag relevant team members or channels for visibility. COMING SOON
Post-release follow-up: Automatically trigger follow-up actions, such as posting open bug lists or checklists for testing validation. Keep the post-release phase transparent and actionable.