Skip to main content
Skip table of contents

Teams: Start a chat/channel conversation

With the Microsoft Teams integration, you can start Teams chats and channel conversations directly from your Jira issue. Enhance your efficiency e.g. by clarifying support tickets with customers through chat, or by triaging tickets with your team via channel conversations.

Customers and team members who do not have access to the Jira issue can still participate in the conversation through Microsoft Teams. Messages, regardless of where they are initiated, are instantly visible in both tools.

Click through demo

Feature at a glance

Using Microsoft Teams in your Jira issues enhances collaboration on tickets, making the process more efficient and user-friendly. It allows for quicker responses to questions and faster delivery of solutions.

Initiate a Microsoft Teams conversation

Once a ticket comes in, the agent can promptly reach out the customer via chat to either request additional information, if necessary, or to inform them that their issue is being addressed.

This does not only enhances customer satisfaction, but also shortens the time to first response, thereby improving service level agreements (SLA).

Through channel conversations, teams can triage tickets directly from your Jira issue, enabling quicker solutions and enhances knowledge sharing.

image-20250613-104118.png

Work with templates

Microsoft Teams chats and channel conversations can be pre-defined via templates, if they are set-up in the global Jira settings.

You can further customize and/or modify the content within the dialogue, if needed. Alternatively, choose a different template from the available options.

image-20250613-104208.png

Define sharing options

When initiating a Microsoft Teams chat or channel conversation, you can customize the sharing settings to control who can access the chat history within the ticket. Especially when the message contains sensitive information, this feature comes in handy.

Typically, in JSM projects, it makes sense to share the chat history with other agents to ensure that no important information gets lost.

πŸ” Private: This respects all Teams default permissions, e.g. only members of the chat can access chat contents.

πŸ‘« Shared: This gives read-only access to all Jira users or JSM agents that have access to this issue, and are logged in with Microsoft Teams.

πŸ—£ Shared & allow joining: This gives read-only access to all Jira users or JSM agents that have access to this issue, and are logged in with Microsoft Teams. In addition, if a user wants to participate in the chat, they can simply join the chat on their own.

image-20250613-104329.png

Benefit from real-time collaboration

Enhance real-time communication across Jira and Microsoft Teams. Initiate chats or channel conversations directly within Jira via MS Teams, and receive instant replies from MS Teams displayed directly in the issue.

All messages and information are instantly accessible in both tools, enabling seamless participation and conversation tracking within MS Teams, even for non-Jira users.

image-20250613-104602.png

Access information centrally (in Jira)

With our Teams integration, all conversation is saved in the Jira issue. Switch between different chats or channel conversations (if access is granted) and join conversations, look up for important information or quickly answer back to a customer. Even meeting chats are available here.

image-20250613-110847.png

Feature configuration

We provide primary configuration options at admin level (refer to: Admin configuration) as well as several minor configurations for individual users (refer to: user configuration below).

User configuration

When working with the Microsoft Teams feature in Jira, users have the ability to customize the chat appearance settings. Customizations can be done via the menu located at the top of the respective chat window.

image-20250612-105758.png

MS Teams chats

image-20250612-105443.png

Add chat participants

To add more participants to the chat, click on the β€œpersons symbol” located in the top bar of the chat window.

This allows you to invite additional team members and share information more effectively.

image-20250612-105541.png

Backup chat to attachments

To backup selected chats as a static PDF in the Jira issue, click on the β€œmenu symbol” located in the top bar of the chat window and retain a record for audits.

The attachment will remain accessible in Jira, even if the chats are deleted in Microsoft Teams.

image-20250612-105616.png

Unlink chat

Select a message and click on the β€œmenu symbol”.

If a conversation was created by mistake or is no longer necessary, you have the option to unlink it.

image-20250612-105642.png

Compact view of chats

Click on the β€œmenu symbol” in the top bar of the chat window.

Similar to MS Teams, we offer a compact view of chats and conversations, displaying information clearer and more concise for users.

image-20250612-105758.png

Compact view of chats
(set a default)

Go to your Microsoft 365 settings in Jira (top right hand corner) and set the default, if the compact view of chats should always be on or off.

MS Teams conversations

image-20250612-110146.png

Unlink conversation

Select a message and click on the β€œmenu symbol”.

You can unlink a conversation, if it was created by mistake or is no longer needed.

Admin configuration

Check the list below for the admin responsibilities associated with the email feature:

πŸ§‘β€πŸ€β€πŸ§‘ Working with Microsoft Teams chats in Jira does not need specific requirements to be met.

The Jira administrator must enable the Teams feature within the global settings. Once this feature is activated, users/agents (in Jira Service Management) will have the capability to reach out to customers via Microsoft Teams chats.

However, to start a Microsoft Teams channel conversation from the issue, requires the installation of our Teams app (free).


β˜‘οΈ Using Jira features in Microsoft Teams requires the installation of our Teams app (free).

Additionally, to also use Jira features in Microsoft Teams (e.g. to create new issues based on chats or channel conversations), the installation of our Teams app (free) is required. The Microsoft Teams team owner (or Microsoft Teams admin) installs and deploys the app for the team.


πŸ› οΈ Configure Teams feature in the admin settings

As an admin you can configure where in the Jira issue the Teams feature should be accessible. Check on the appearance settings.

Chat participants

When using our Teams feature, the chat functionality works for all team members in your company.

In certain situations, it may be necessary to engage in a chat with external or guest users. Below, you will find more information on steps you can take.

External users/Guest users

Creating a chat with external users (Business Accounts on Office 365) works the same way as with internal users. Just enter the email address of the external contact when creating a chat.

Please note: We’re not able to check in advance, if a chat with the user will be possible. There are a few requirements for this to work (see below).

image-20250611-105328.png

Requirement: Check user availability

In order to start a chat with an external user, certain requirements need to be met:

  • The external contact has a MS Teams account for their email address

  • Permissions: the organization of the external contact needs to allow chats with your organization

  • Permissions: Your organization needs to allow chats with the external organization

Follow instruction to check, if a chat is possible:

Start a chat in MS Teams
Open a new chat in Microsoft Teams and enter the email address of the contact.
After clicking on β€œsearch externally”, you can receive two messages (see below).

Option 1: error message

Meaning, the user has no Teams account for this email address at all.

Option 2: error message

Your organization or the external users organization has restricted external chats. See below for help on this.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.