We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-14053

Asset: Asset should automatically remove the user account from attribute value if the user account is deactivated.

    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      Assets is used as a single source of truth. If the user account is defined as a owner for service in Asset, and that account is deactivated in user management, it doesn't sync into Asset. Today, a lot of customers use automation to auto set a 'Request Participant' in Jira issue, and if the account is inactive, it will error out. Admins will have to manually remove the user account from attribute value.

      Suggested Solution

      When an user account is set to inactive, Asset should automatically remove the user account if it's present in user type attribute.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Jira Service Management Cloud'
            1. Jira Service Management Cloud
            2. JSDCLOUD-14053

            Asset: Asset should automatically remove the user account from attribute value if the user account is deactivated.

              • 2
              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                Problem Definition

                Assets is used as a single source of truth. If the user account is defined as a owner for service in Asset, and that account is deactivated in user management, it doesn't sync into Asset. Today, a lot of customers use automation to auto set a 'Request Participant' in Jira issue, and if the account is inactive, it will error out. Admins will have to manually remove the user account from attribute value.

                Suggested Solution

                When an user account is set to inactive, Asset should automatically remove the user account if it's present in user type attribute.

                        Unassigned Unassigned
                        b6d0a675f06c Remo Fernandes
                        Votes:
                        7 Vote for this issue
                        Watchers:
                        7 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            b6d0a675f06c Remo Fernandes
                            Votes:
                            7 Vote for this issue
                            Watchers:
                            7 Start watching this issue

                              Created:
                              Updated: