Project automation: Jira Software
About
Project automations save time and effort managing development projects across teams. Clear and consistent information among team members improves work and documentation efficiency.
Our project automations are simple to set up and offer multiple configuration options to fit your needs.
For Jira Software, there are three automation types:
Usage recommendation
RELEASE CHANNEL
As soon as a new release starts, our app will automatically post an adaptive card into a dedicated Teams channel where stakeholders can get an overview about the overall timeframe and duration, included work items and progress of those, not yet being finished.
Although information is shared in MS Teams, this automation does not aim to open discussions or active exchanges on releases between stakeholders and development teams. It rather focuses to transparently provide necessary information to stakeholders who rely on updates.
SPRINT CHANNEL
As soon as a new sprint starts, the automation will post an adaptive card with relevant key sprint information to a predefined Teams channel. As work items change their status (from To Do → In Progress → Done), stakeholders can track this progress in the respective channel.
Sprint Channel automation basically works like the release channel automation and is also primarily used to provide relevant information and updates on projects for stakeholder.
Like release channel automations, this automation does not aim to spark discussion or exchange about the sprint in MS Teams. Instead, it focuses on consistently sharing project transparency with the relevant stakeholders involved in the project.
CLIENT CHANNEL
Use the Client channel automation when clients or stakeholders regularly share feature requests, improvements, or other actionable feedback in a Microsoft Teams channel.
For a channel dedicated to new requests, configure the automation to create a Jira work item from every new post. For a channel that also contains general discussion, use a keyword reply so team members can decide which conversations should become Jira work.
The Teams thread remains linked to the newly created work item. Clients can continue the conversation in Teams while the development team plans and tracks the work in Jira.
EPIC CHAT
Whenever a new epic is created, the automation will initiate a Teams chat with a set of predefined participants. Team members across departments can join the conversation from Teams, too and information is shared across Jira and Teams.
If configured, the chat is also accessible in all child work items of the corresponding epic.
Epic chat automation helps the team to exchange and discuss on current projects and provides a communication hub for developers.
This automation type is primarily used for internal collaboration on epics and their work items.
Release channel
Our release channel automation initiates a Microsoft Teams channel post whenever a new release has started.
This way, all participants involved in the channel will be informed about its current status and progress (including all included work items related to it) while information is constantly shared transparently across Jira and Teams.
If individual work items of a release are not yet finished, this can be tracked and seen via the adaptive card.
Configure the automation to your specific needs and align it with your projects' different purposes and your team’s overall way of working.
Sprint channel
Our sprint channel automation initiates a Microsoft Teams channel post whenever a new sprint starts. All participants involved in the channel will be informed about the current status and progress of included work items of the sprint.
Use this automation specifically when stakeholders need to be involved and regularly informed about the current status of a project. As sprints focus on a specific time frame and aim to deliver relevant parts of a final product or service, it can be important to maintain transparency with customers and enable them to contact people involved in the sprint via MS Teams.
Configure the automation to your specific needs and align it with your projects' different purposes and your team’s overall way of working.
Configure an adaptive card
Currently, you can only use our “default release card”. In future, it will be customizable, allowing you to choose among different adaptive cards.
Client channel
The Client channel automation turns selected Microsoft Teams channel conversations into Jira work items and keeps the original thread linked to Jira.
When the configured trigger occurs, Microsoft 365 for Jira creates a work item using either:
The content of the top-level Teams message, or
An AI-generated summary of the complete conversation thread
Use the top-level message when the initial post already contains a complete and structured request. Choose an AI summary when requirements, decisions, or technical details emerge through the replies. The AI summary brings this information together as an actionable work item description which can be edited later in Jira, if required.
Using AI-generated summaries requires AI features to be enabled in the global Jira settings for Microsoft 365 for Jira settings. Generated content should be reviewed before implementation begins.
Configure the automation to your specific needs and align it with your projects' different purposes and your team’s overall way of working.
Epic chat
When a new epic is created, our epic chat automation instantly starts a Teams chat with a predefined number of team members of your space.
If configured, the epic chat can be accessible in each child work item, ensuring full project transparency across the team.
Use epic chats to share updates, request approvals or reviews, and discuss challenges with all people involved.
Configure the automation to your specific needs and align it with your projects' different purposes and your team’s overall way of working.
Use Epic chat automations for any other issue type as well, such as stories, tasks and bugs.
Configuring epic chats
Our epic chat automation combines several configuration options of our Microsoft 365 for Jira app. We recommend reviewing them first before jumping into the set-up itself. In the section below we want to outline steps which require attention and preparation.
Of course, you can configure them during the set-up process of the automation via the arrow next to the individual steps.
Set-up a service user
When configuring the epic chat automation you need to define a service user. It is this neutral user who initiates Teams chats on behalf of the app until an agent or team member jumps in.
Since this automation starts MS Teams chats automatically whenever a new epic is created (which is not necessarily your personal project), you should not use your personal credentials as the sender.
Follow the link (arrow) next to the service user tab to set them up.
The service user enables faster communication and makes information about new projects centrally available.
Please keep in mind, that the service user requires a Microsoft Teams license.
Learn more about service users.
Set-up a chat template
Select a suitable template as the basis for the initial chat message posted by the Service User when a new epic is created.
We recommend to set-up a template before configuring the automation. To do so, go to your space settings. Alternatively, you can do so when clicking on the arrow.
If there is already a template at hand, conveniently select it via the drop down menu.
Make sure, that the message aligns with the purpose of the chat and may already contain overall information / next steps for the team.
Set-up a Teams chat Preset
Chat behavior and subsequent actions after posting the chat to MS Teams, depend solely on the preconfigured Preset (keyword: built-in automation).
It is the Preset that will kick off actions like adding a JSM comment to the work item after the chat has been started. Or that the chat will be backed up as a PDF file, if the work item is resolved, for example.