- 23 Feb 2025
- 3 Minutes to read
- Print
- DarkLight
- PDF
TeamDynamix - Create Ticket
- Updated on 23 Feb 2025
- 3 Minutes to read
- Print
- DarkLight
- PDF
TeamDynamix - Create Ticket creates a ticket in TeamDynamix for:
- Assets returned by the selected query or assets selected on the relevant asset page.
- Not all asset categories are supported for all Enforcement Actions.
- See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.
- See Actions supported for Vulnerabilities.
- See Actions supported for Software.
Required Fields
These fields for TeamDynamix tickets must be configured to run the Enforcement Set.
- Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
- Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.
Use stored credentials from TeamDynamix adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
- When you select this option, the Select Adapter Connection drop-down is available, and you can choose which adapter connection to use for this Enforcement Action.
Note:To use this option, you must successfully configure a TeamDynamix adapter connection.APP ID - The ID of the application.
Ticket Title - The title of the ticket.
Type ID - The ID of the ticket type.
Status ID - The ID of the ticket status.
Priority ID - The ID of the ticket priority.
Requestor UID - The UID of the user requesting the ticket.
Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Connecting Additional Axonius Nodes.
Additional Fields
These fields are optional.
Connection and Credentials
When Use stored credentials from the adapter is toggled off, some of the connection fields below are required to create the connection, while other fields are optional.
- Host Name or IP Address - The hostname or IP address of the TeamDynamix server.
- User name and Password - The credentials to connect to TeamDynamix.
- Verify SSL (optional) - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.
- HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.
- HTTPS Proxy User Name (optional) - The user name to use when connecting to the server using the HTTPS Proxy.
- HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.
- Brief Description - Enter a short description of the issue in the ticket.
- Add default ticket description - This description will be added to tickets.
- Parent ID - The ID of the parent ticket.
- Account ID - The ID of the user account creating the ticket.
- Group Name - The name of the group that owns, manages, or is directly associated with the ticket.
- Responsible Group ID - The ID of the group responsible for resolving, acting on, or ultimately accountable for the ticket.
- Attach a CSV file with the affected entities - When selected, the enforcement action will create a CSV file with the details of the query results that triggered the ticket creation.
- Link the affected entities to the created ticket - When selected, the assets related to the ticket are linked to the ticket.
- Gateway Name - Select the Gateway through which to connect to perform the action.
API
Axonius uses the TeamDynamix Web API: Tickets.
Required Permissions
The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:
- Write/Admin permissions
For more details about other Enforcement Actions available, see Action Library.