Preset for the Microsoft Teams feature can be defined for chats and channel conversations. Learn more about the configuration process below.
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 framework
Framework settings
not editable by the user
Create your Preset for all or only JSM projects.
Decide on a name and description. Find a little preview of your Preset on the right.
Preset features | Decide between Jira or JSM projects. |
Preset name | Choose a specific name so that users understand the usage of the Preset. |
Preset icon | Choose a suitable icon for 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. |
Default 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.
Set defaults
editable by the user
Decide on chat title and message content (based on a template), participants and chat access options here.
The user can edit these settings in the issue, if desired.
Chat title & message | Choose among established chat templates which content should be prefilled with a Preset for your Teams chats. Give the chat Preset a title. |
Participants | Static user: Search by email for a required persons. |
Chat access | Decide whether to share the content of the chat or to keep it private. |
Notifications in Microsoft Teams
Only one app per Preset can be selected!
Notification settings
not editable by the user
For Teams chats, you can choose which app should post updates about the issue or request to the relevant Teams chat.
Teams app | Selectable with Preset features: Jira projects Operating as a bot, our Smart Connect app will post updates into the corresponding chat. This has to be approved by your Microsoft admin. As soon as notification options have been selected, they are automatically added as respective built-in automations.  |
Teams portal app | Select with Preset features: JSM projects If the Preset is set up for JSM projects, the admin can choose among the customer portal or Smart Connect bot. Teams portal bot (referred to as “IT support” below): Customer-related updates will be posted in the existing customer chat. We recommend using this for customer-facing notifications. As soon as notification options have been selected, they are automatically added as respective built-in automations.  |
Built-in automations
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. No manual setup is required. These settings are active throughout the chat's lifecycle and have no automation service limit.
Automate workflows
not editable by the user
Use automation rules to make workflows more efficient in your Jira or JSM project.
Available built-in automation options | |
Chat created | Whenever a Teams chat is created, a Jira comment will be added to the issue (and involved persons will be notified via email) |
Chat created | Choose a transition of the issue to apply when the chat is created. Select among options provided.  Emoji :pushpin: Please note:
|
Chat created | The user will automatically be assigned to the issue, if they start a chat (provided that the user has permissions to assign themselves). |
Issue resolved | 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:  |
Issue resolved | Hide the chat connected to this Preset in Microsoft Teams. Reporter, customer users and request participants will still be able to see the chat. |
Issue resolved | 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. |
If you want to set up more advanced Jira automation rules with Microsoft 365, click here.
Finish set-up
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. Emoji :pushpin: 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. Emoji :pushpin: Please note: Project specific settings will be overridden and the Preset will automatically be available and selectable in the Jira issue. |