Automation: Actions

Create Teams chat

Send a message in a Teams chat and include the participants of your choice. This action will fire the ‘Chat created’ trigger when completed.

Please note for JSM usage: The chat creator must be a single user and will always be part of the chat. We recommend to create a new service user until we support dynamic user selection.

• Chat title

• Chat creator

• Chat member

• If a guest user is available for the chat member, choose to prioritize inviting them before attempting to add an external user.

• Chat message

• Chat access (shared & allow joining, shared, private)

• Choose to post notifications

When an issue goes into the Jira status ‘review’, start a group chat with the reviewer and the assignee to discuss the review.

Reply Teams chat

Reply to all Teams chats linked to the issue, that have the bot installed (you will need to enable notifications via the Teams portal app).

• Teams bot (sender of the message)

• Chat type

• Chat message

Post an additional message after resolving a request to inform the participants that this chat cannot be used for further communication, and advise them to submit a new request if they require further assistance.

Create Teams channel conversation

Post a message in a Teams channel of your choice. This action will also fire the ‘Conversation created’ trigger when completed.

• Teams bot (sender of the message)

• Channel in Teams

• Message type (issue card or custom message)

Use a dedicated, monitored Teams channel to be notified of escalating issues, either customer request or in development / operations. This action can be triggered by any Jira automation trigger, e.g. when an issue is set to ‘Escalated’ status, or a critical priority.

Reply Teams channel conversation

Add a comment to all Teams conversations linked to the issue the user posting the reply has access to.

• Teams bot (sender of the message)

• Conversation type

  • all linked conversations

  • single conversation (available only for web request body > custom data)

• Conversation message

When a Teams conversation is already linked to an issue reply to that conversation that the SLA of first response of that issue is about to breach shortly.

Backup Teams messages

Add a backup file for each chat and channel conversation to the Jira issue.

Side note: You can work with built-in automations to create backups, too.

• Backup all Teams chats

• Add a comment with keywords to the Jira issue

When the Jira issue is set to 'Done', the action is triggered to export all the information in the Teams chat and channel conversations to a static PDF file, which is added to the Jira issue, for example, for auditing purposes. Even if the chat or conversation has been deleted in Microsoft Teams, the static PDF file is still documented in your Jira issue. You can also add conversation keywords to the comments section.

Send bot message

Send a bot message to a user who has installed the Teams bot.

• Teams bot (sender of the message)

• Message recipients (User field)

• Message

When a bug has been created and an assignee is set, send him a customized bot message to inform him about the content of the ticket.

Send Outlook email

Send an email to the recipients of your choice.

• Sender (Only email addresses from your Azure Active Directory tenant can be added)

• Recipients (CC, BCC)

• Subject

• Message

• Shared email access (private, organization, issue access)

• Send only in working hours

If the Jira ticket has transitioned to a configured status, the action is used to send a status report to the stakeholder.

Create Outlook meeting

Send a meeting to the participants of your choice.

• Sender (Only email addresses from your Azure Active Directory tenant can be added)

• Subject

• Attendees and optional attendees (User field)

• Start date time (Parsed from an issue field)

• Meeting duration

• All-day

• End date time (Parsed from an issue field or fixed to start date)

• Location incl. MS Teams meeting link

• Description

• Show as

• Reminder

• Private meeting

• Category

• Timezone

• Shared meeting access (public, private)

When the Jira issue is set to ‘Review’, create an Outlook meeting with the reviewer and the assignee.