Teams portal app: How can I create an API token to enable Asset field support?

If you want to have your JSM portal neatly integrated in MS Teams, please consider the following information and required steps below.

Teams portal app settings

To display your JSM portal identically in MS Teams, including Assets fields being configured in some JSM spaces, toggle on the “native look and feel” option in the Microsoft 365 for Jira admin settings.

Next, set up an API token to enable synchronization between Jira and MS Teams.

The API token can basically be set-up in two ways:

1. Create an API based on a Jira user (usually a Jira admin)

2. Create an API token based on a Jira service account using

1. Create an API token based on a Jira user

To create an API token simply follow instructions as mentioned in product. Enter your email address and click “create new”.

Advantages

• The admin user creates and thus, “controls”/relates with the token

• Asset fields and Affected Service fields can be displayed

Disadvantages

• The token is removed when the user is deactivated in Jira

• Only the user controls the token

2. Create an API token based on a Jira service account

At first, go to your Jira administration page and select an instance to create a new service account.

Select Service accounts to create a new service account as the basis for the API token.

To create an API token using a service account, follow the steps in the video below. First, set up an email address to being able to generate the API token afterwards.

Advantage

• The token is linked to a service account that remains in your Jira instance.

• Every admin with access to service account configuration controls the token

Disadvantage

• Due to limitations, only Assets fields, but not Affected Services fields, will be displayed later in MS Teams