Sync Asana File Attachments to Jira Issues
Your designer uploads a spec to Asana, and it instantly appears in the Jira issue too. No hunting for attachments across two windows, no forgotten context.
Trigger
Attachment Added to Task
Triggers when an attachment is added to a task.
Action
Add Attachment
Uploads and attaches a file to a jira issue.
Why this helps
Files live in Asana, but developers work in Jira. You end up uploading the same attachment to both, or worse, developers miss the spec because it's only in Asana.
- Designers upload once; developers see it everywhere
- No forgotten attachments or repeated uploads
- Design context stays with the issue throughout its lifecycle
- Reduce friction in design-to-dev handoff
Setup
Build it in a few focused steps.
- 1Connect Asana and Jira to Notis (one-time per workspace).
- 2Tell Notis 'When a file is attached in Asana, add it to the matching Jira issue' or build it in the portal automation wizard.
- 3Select 'Attachment Added to Task' as the trigger and choose your notification channel.
- 4Attach a test file to an Asana task linked to a Jira issue—you'll see it appear in Jira within seconds.
Questions about this workflow
How does Notis know which Asana task matches which Jira issue?
You link the two during setup (e.g., via task URL or custom field). Notis remembers the connection and automatically syncs attachments between them.
What file types are supported?
Any file Asana and Jira accept—PDFs, images, documents, design files, videos. Notis passes them through as-is.
Can I exclude certain files?
Yes. Refine your prompt: 'Add attachments to Jira, but skip any files named draft or with sensitive in the name.' Notis will filter accordingly.
What happens if a file is deleted from Asana?
The attachment stays in Jira (Notis doesn't remove it), but you can modify the automation to delete it if you prefer.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Asana to Jira. A trigger fires from one place; an action lands in another.
Asana triggers
Jira actions
Attachment Added to Task
Triggers when an attachment is added to a task.
Add Attachment
Uploads and attaches a file to a jira issue.
New Comment on Task
Triggers when a comment is added to a task in a project.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
New Task Created
Triggers when a new task is created in a project.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Task Moved to Section
Triggers when a task is moved to a section in a project.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Tag Added to Task
Triggers when a tag is added to a task. Note: Asana's event structure is inverted for tag events — the resource is the task and the parent is the tag. So parent.gid gives the tag GID.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Task Updated
Triggers when a task is updated in a project.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Not just Asana and Jira. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Jira.