選取您的 Cookie 偏好設定

我們使用提供自身網站和服務所需的基本 Cookie 和類似工具。我們使用效能 Cookie 收集匿名統計資料,以便了解客戶如何使用我們的網站並進行改進。基本 Cookie 無法停用,但可以按一下「自訂」或「拒絕」以拒絕效能 Cookie。

如果您同意,AWS 與經核准的第三方也會使用 Cookie 提供實用的網站功能、記住您的偏好設定,並顯示相關內容,包括相關廣告。若要接受或拒絕所有非必要 Cookie,請按一下「接受」或「拒絕」。若要進行更詳細的選擇,請按一下「自訂」。

Configuring core operational settings

焦點模式
Configuring core operational settings - AWS Service Management Connector
此頁面尚未翻譯為您的語言。 請求翻譯
To configure operational settings for the AWS Service Management Connector for Jira Service Management
  1. In the left navigation menu, under AWS Service Management Connector, choose Connector settings.

  2. Under Core operational settings, in the Synchronization interval field, you can change the sync interval if you want.

    This interval determines how often Jira Service Management syncs with AWS. Increasing this number reduces the number of API calls to AWS, but increases the time for updates in AWS portfolios and automation documents to reflect in the Connector. Information on actively provisioning products and ongoing automation executions updates are more frequent.

  3. Under Core operational settings, in the JIRA Administrator to run as field, you can change the admin user assigned to perform automated operations within JIRA.

    Important

    The Connector performs many actions within Jira, and needs to do those actions as a Jira user. By default, Connector chooses the Jira Admin user with the lowest ID, which works for many environments.

    However, that approach might be the wrong strategy if the initial admin user has been disabled, or if there is a different admin user. For clarity within the Connector, it can be a good idea to create a new user called, for example, "AWS Connector Admin", and select that as the default user.

    We record actions performed automatically by the Connector as being performed by this user, such as synchronizing OpsItems from AWS or adding a comment for changes to an AWS provisioned product. These actions do not affect actions that end users perform, such as requesting a provisioned product or manually creating an OpsItem in Jira, which we record as the end user performing the action.

    This user should have global admin permissions, JSM permissions, and admin access to each of the AWS-enabled projects.

  4. Choose Save.

Note

We recommend no changes to entities that the plugin created, such as the addition of fields, workflows, issue types, screens, and so on.

隱私權網站條款Cookie 偏好設定
© 2025, Amazon Web Services, Inc.或其附屬公司。保留所有權利。