Adstudio writes the Jira ticket from what it found in the account. Every ticket, comment and edit is proposed as a card you click to approve.
Drafted in ADS with the evidence attached. Nothing is created until you approve.
Frequency on Lookalike 3% passed 6 in October and CTR is falling. Refresh the creatives before the next budget shift.
Lookalike 3% · last 14 daysFrom a chat, a signal or a finding. Adstudio fills in the summary, the evidence and the campaign, in your project.
When the data changes, Adstudio proposes the update — the old value and the new one side by side, never a silent overwrite.
The ticket carries the evidence in its description and the campaign as a link — on a new ticket or one your team already has.
No. Every new ticket, comment, edit and status move is proposed as a confirmation card, and nothing reaches Jira until you click it.
It can create a ticket, comment on one, attach a campaign link, edit the summary, description, due date or labels, and move a ticket through your workflow. It has no way to delete a ticket or reassign an existing one.
Jira Cloud, connected with your Atlassian account from the workspace's integrations.
No. Jira and the task board are separate destinations; Adstudio uses Jira when you ask for it.