-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
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.
- was cloned as
-
JSDSERVER-15675 Asset: Asset should automatically remove the user account from attribute value if the user account is deactivated.
- Gathering Interest
Asset: Asset should automatically remove the user account from attribute value if the user account is deactivated.
-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
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.
- was cloned as
-
JSDSERVER-15675 Asset: Asset should automatically remove the user account from attribute value if the user account is deactivated.
- Gathering Interest