Skip to end of banner
Go to start of banner

TFS4JIRA Self-Hosted | User mapping in database

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

This article provides information how user mapping is stored in the TFS4JIRA database.

TFS4JIRA SELF-HOSTED can use following database servers:

  • SQL Compact Edition (default database)

  • Firebird

  • MS SQL Express/Full

JIRA

 expand to see details

To get Jira users we use /rest/api/latest/user/assignable/multiProjectSearch?projectKeys=mappedProjectKey and get only those with accountType equal to atlassian.

Examples:

Jira Cloud: https://damkil.atlassian.net/rest/api/latest/user/assignable/multiProjectSearch?projectKeys=STA40&query=damian

query string

A query string that is matched against user attributes, such as displayName and emailAddress, to find relevant users. The string can match the prefix of the attribute's value. For example, query=john matches a user with a displayName of John Smith and a user with an emailAddress of johnson@example.com. Required, unless accountId is specified.

Jira 9.4: http://52.2.97.38:8080/rest/api/latest/user/assignable/multiProjectSearch?projectKeys=TES&user=damian

from Jira 8.20.7 parameter: username | string | the username

 

Jira version

In DB

endpoint value

comment

Cloud

[JiraAccountId]

"accountId"

 

Cloud

[JiraUsername]

NULL

 

Both

[JiraDisplayName]

"displayName" <"emailAddress">

this value only setup what is shown in the UI in TFS4JIRA

On-Premise

[JiraAccountId]

NULL

 

On-Premise

[JiraUsername]

"name"

 

  • No labels