Skip to main content

​
Overview

The “Create Ticket” feature lets you export work from Gradial to your external ticketing system. This is useful when:
  • Work originates in Gradial and needs to be tracked in Jira
  • You want to create follow-up tickets based on AI analysis
  • You need to batch-create tickets for multiple items

​
How It Differs from Ingestion

AspectNormal IngestionCreate from Gradial
DirectionExternal → GradialGradial → External
SourceExternal ticket exists firstGradial thread exists first
Use casePull existing work into GradialExport Gradial work to external system
Link createdYesYes
Once created, the external ticket link works the same way—bidirectional sync keeps both sides in sync.

​
Requirements

To create external tickets from Gradial:
  • You must have an active integration with the target system (currently Jira)
  • The Gradial thread must be a native Gradial thread (source = GRADIAL), not an already-synced external ticket
  • You need appropriate permissions in the external system to create tickets

​
Creating a Single Ticket

  1. Open a Gradial thread you want to export
  2. Click the Create Jira Ticket button (or access via the thread menu)
  3. Configure the ticket details:
FieldDescription
IntegrationSelect which Jira integration to use
ProjectChoose the target Jira project
Issue TypeSelect the issue type (Story, Task, Bug, etc.)
AssigneeOptionally assign to a team member
PrioritySet the ticket priority
LabelsAdd Jira labels
  1. Click Create Ticket
Gradial will create the ticket in Jira and establish a bidirectional sync link.

​
Batch Creating Tickets

For parent threads containing multiple child items (like a campaign or batch), you can create tickets for all children at once:
  1. Open the parent thread (folder, batch, or campaign)
  2. Click Create Jira Ticket
  3. Select Create tickets for each subtask
  4. Configure common settings that will apply to all tickets:
    • Target project
    • Issue type
    • Common labels
  5. Review the list of items that will become tickets
  6. Click Create X Tickets
Each child item will get its own Jira ticket, all with consistent settings.

​
What Gets Included in the Ticket

When you create a Jira ticket from Gradial:
ContentIncluded
TitleThread title becomes issue summary
DescriptionThread description/initial message becomes issue description
AttachmentsThread attachments are uploaded to the Jira ticket
ContextLink back to Gradial is included in the description

​
After Creating a Ticket

Once the external ticket is created:
  • Sync is active — Changes in either system will sync to the other
  • Comments sync — New comments flow both directions
  • AI processing — If someone @mentions Gradial in the Jira ticket, AI will process the request
  • View in Jira — Click the external link icon to jump directly to the Jira ticket

​
Limitations

Currently supported systems: Jira only. Wrike and Workfront support for creating tickets from Gradial is planned. Attachment sync: Depending on your Jira authentication method, attachments uploaded from Gradial may not sync to Jira. This is a known limitation with certain auth configurations. One-way creation: You can create a ticket from Gradial, but you cannot “un-link” or reverse the connection once established.

​
Best Practices

Use descriptive titles — The Gradial thread title becomes the Jira summary, so make it clear and actionable. Add context in description — Include relevant background so the Jira ticket is self-contained. Choose the right project — Select the Jira project that matches your team’s workflow. Set appropriate issue type — Match the work type (Bug for defects, Story for features, Task for general work).