Asana - Create Ticket

Asana - Create Ticket creates a ticket in Asana for:

  • Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

📘

Note:

Required Fields

These fields 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 Asana 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 becomes available. Select the adapter connection to use for this Enforcement Action.

📘

Note

To use this option, you must successfully configure a Asana adapter connection.

Additional Fields

These fields are optional.

  • Task Name - Enter a name for the task.

  • Resource Subtype - Enter the resource subtype for this task.

  • Completed - When selected,

  • Due On - Select a due date for this task.

  • Description (Notes) - Enter a description of the task.

  • Assignee GID - Enter the GID of the task assignee.

  • Followers - Add a list of users that will follow this ticket.

  • Parent Task GID - The GID of the parent task, if any.

  • Workspace GID - The GID of the Asana workspace this task will be added to.

  • Gateway Name - Select the Gateway through which to connect to perform the action.

💡

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.

  • Asana API URL (default: https://app.asana.com) - The hostname or IP address of the Asana server.

  • Access Token - Enter your API access token.

  • Capture Users from Workspaces - Users from the listed workspaces are captured and added to the ticket. Enter a comma separated list of either Workspace names or Workspace GIDs.

  • 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.

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have permission to perform this Enforcement Action.

APIs

Axonius uses the Asana API


For more details about other Enforcement Actions available, see Action Library.