-
Suggestion
-
Resolution: Fixed
-
None
Problem description
Currently, Rovo instance administrators can only delete Rovo Agents associated with deactivated accounts. When managed Atlassian accounts are deactivated, admins can access the Rovo Agent profile created by others and transfer ownership to their own accounts. This allows them to delete the agent afterward.
They also don't have a way to delete OOTB or any type of System Rovo Agents at all.
Suggested solution
Provide a way to Admins to delete any type of Rovo Agent from their Rovo instances, including but not limited to Rovo Agents created by others, Rovo Agents OOTB, and others.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- mentioned in
-
Page Loading...