Skip to main content
Skip table of contents

Preset: Teams

Preset for the Microsoft Teams feature can be defined for chats and channel conversations. Learn more about the configuration process below.

image-20241111-155352.png

Configure a Preset for Teams chats

Click through this short demo to configure a Preset for Teams chats.

Configure a Preset for Teams Channel conversations

Click through this short demo to configure a Preset for Teams channel conversations.

Preset settings

Preset blueprints

image-20250926-090855.png

You can create presets from scratch (first two options) or from a preconfigured blueprint (see options below under “recommendations”). Blueprints are available for specific use cases, such as incident chat or internal chat.

Teams chat/channel Preset blueprints provide pre-filled configuration options for:

  • Participants (Jira or static field)

  • Access options (sharing)

  • Chat notifications

  • Built-in automations

You can adjust or accept these options.

When creating a Preset, you can choose between a JSM or Jira project. Configuration options differ based on the Preset type.

Preset framework

image-20250910-092246.png

Framework settings
NOT EDITABLE BY THE USER

When selecting a Preset option, decide on a name & icon, a tag and add a short description.

Preset icon & name

Choose a specific name and icon so that users understand the usage of the Preset.

Preset tag

Use tags e.g. “internal” / “external” / “sensitive” etc. to categorize the Preset for the user.

Preset description

Be as precise as possible to distinguish easier among your Presets.

Chat/channel post settings

To access chat participants or MS Teams channels, you must log in with your Microsoft 365 account via this button on the bottom of the page. image-20241112-082933.png

image-20250926-091359.png

Set defaults
EDITABLE BY THE USER

Decide on participants (Jira field or MS user). Add a template to define the message content when using the Preset. Set access options (sharing content).

The user can edit settings in Jira, if required.

Participants

Static user: Search by email for a required persons.
Jira field: Enter a Jira field term to be added here.

Template

Choose among defined chat/channel templates to define the message content when using the Preset in Jira.

Create a global Preset:
Only globally defined templates can be accessed.

Create a project specific Preset:
Globally and project specific templates can be accessed.

Create a new template:
If existing templates do not meet your criteria, set up a new one directly from the Preset configuration.

Access

Decide whether to share the content of the chat or to keep it private.

Chat notifications

Only one app per Preset can be selected!

image-20250910-093113.png

Notification settings
NOT EDITABLE BY THE USER
For Teams chat Presets, you can choose which app should post updates about the work item or request to the relevant Teams chat.

Smart Connect app
(Teams app)

If the preset is for Jira projects, only the Smart Connect app is available. The Teams portal app is hidden.

Operating as a bot, our Smart Connect app will post updates (as selected) into the corresponding chat/channel.

image-20250910-094339.png

Helpdesk
(Teams portal app)
JSM ONLY

If the Preset is set up for JSM projects, the admin can choose between the Teams app or Teams portal app.

Teams portal bot (referred to as “Helpdesk” below):
Customer-related updates will be posted in the existing customer chat/channel.
We recommend using this bot for customer-facing notifications.

Smart Connect bot:
Only those changes to the work item as being selected here, will be posted into the relevant chat/channel.
Use this bot especially for internal communication, like triage cases.

image-20250910-094925.png

Built-in automations
NOT EDITABLE BY THE USER

Please note:
Chat notifications (see above) will automatically be configured as built-in automations.

Choose from built-in automations that integrate Microsoft 365 features with Jira and make workflows more efficient in Jira and/or JSM projects. No manual setup is required. These settings are active throughout the chat's lifecycle and have no automation service limit.

image-20250912-100045.png

JSM projects

Chat created
>> JSM comment

Whenever a Teams chat is created, a comment will be added to the request (and involved persons will be notified via email).

Chat created
>> Assign user to request

The user will automatically be assigned to the request, if they start a chat (provided that the user has permissions to assign themselves).

Chat created
>> Call chat

As soon as a chat is started from Jira related to the request, a MS Teams call will automatically be initiated with all involved people.

This can be helpful when requests need to be solved quickly.

Request resolved
>> Chat backup*

Generate a backup of the Microsoft Teams chat linked to this Preset and attach it as a PDF file in the Jira issue.

Prompt a summary as a comment when the following toggle is enabled and choose the language:

image-20250910-095806.png

Request resolved
>> Hide chat

Hide the chat connected to this Preset in Microsoft Teams.

Reporter, customer users and request participants will still be able to see the chat.

Request resolved
>> Remove reporter and request participants from chat

Reporter and request participants will be removed from the Microsoft Teams chat, once the issue is resolved.

This is useful in a JSM context, so customers won’t use the existing communications for new topics. However, they will not be able to complete the CSAT survey.

PROJECT SPECIFIC
Chat created
>> Transition request

Choose a transition of the request to apply when a chat is created. Select among options provided.

image-20250912-100413.png

Please note:

  • Only transitions without screens are available.

  • Only one “any status” can be selected.

  • Multiple transitions from specific status can be selected.

PROJECT SPECIFIC
Chat message received (after resolution)
>> Transition request

Choose a transition when a new message appears in a related chat of an already resolved request. Select from the provided options.

image-20250912-100441.png

Jira projects

Chat created
>> Jira comment

Whenever a Teams chat is created, a Jira comment will be added to the work item (and involved persons will be notified via email).

Chat created
>> Assign user to Jira work item

The user will automatically be assigned to the work item, if they start a chat (provided that the user has permissions to assign themselves).

Chat created
>> Call chat

As soon as a chat is started from Jira related to the work item, a MS Teams call will automatically be initiated with all involved people.

This can be helpful when requests need to be solved quickly.

Work item resolved
>> Chat backup*

Generate a backup of the Microsoft Teams chat linked to this Preset and attach it as a PDF file in the Jira issue.

Prompt a summary as a comment when the following toggle is enabled and choose the language:

image-20250910-100748.png

Work item resolved
>> Hide chat

Hide the chat connected to this Preset in Microsoft Teams.

Reporter, customer users and work item participants will still be able to see the chat.

PROJECT SPECIFIC
Chat created
>> Transition work item

Choose a transition of the work item to apply when a chat is created. Select among options provided.

image-20250912-100549.png

Please note:

  • Only transitions without screens are available.

  • Only one “any status” can be selected.

  • Multiple transitions from specific status can be selected.

If you want to set up more advanced Jira automation rules with Microsoft 365, click here.

Finish set-up

image-20250910-100358.png

Create Preset
NOT EDITABLE BY THE USER

When finishing the set-up of the Teams Preset, you can decide between different activation options.

Create only

Create the Preset and it will be available in the admin / project settings in Jira. It needs to be manually activated via the settings.

Create + activate globally

Create and activate the Preset and it is automatically active in all Jira projects with no project-specific settings.

📌 Please note: If there are project specific settings, the project admin still needs to activate the Preset manually via the project settings.

Create + force activation

Create and activate the Preset and it is automatically active in all Jira projects regardless of project-specific settings.

📌 Please note: Project specific settings will be overridden and the Preset will automatically be available and selectable in the Jira issue.

JavaScript errors detected

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

If this problem persists, please contact our support.