![]() Setting connection timeout for JIRA endpoints.Therefore, when an application uses an API key to access ALM, the application is limited by its user's permissions.You can use an API key to access ALM only if it is currently listed as active in the list of API keys.ĪLM 12.60: For more details see, What's New in ALM 12.60.ĪLM 14.0X: For more details see, What's New in ALM 14.0X. Each API key is associated with an ALM user. Each API key includes a Client ID and an API Key Secret for applications to use when authenticating. The ALM site administrator generates and manages the list of API keys for ALM. API key authentication provides a secure authentication mechanism for external applications accessing ALM's API. ALM Synchronizer supports API Key authentication for API integrations.For details on how to create an API token, see. To set the JIRA connection properties for JIRA endpoints, you generate an API token from your Atlassian account, then copy and paste it to the Password field. Use an API token to authenticate an Atlassian Cloud version of JIRA.Send notifications to multiple email addresses: You can instruct Synchronizer to send notifications to multiple email addresses that are separated by commas or semicolons.Support requirement target cycle sync: Support mapping with the ALM Target Cycle field for requirement synchronization.Formatting of comments is retained during synchronization (in either direction). Comments sync between ALM and JIRA is enhanced: Support comments sync using the ALM REST endpoint.You can either set default values for required fields or just use the system pre-defined values. ![]() When Synchronizer creates new entities, and if the optional field is empty, a default value is assigned to the required field.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |