Sync Asana Tags to Jira Priority Automatically
Tag a task as 'critical' in Asana and it instantly becomes a High-Priority issue in Jira. Your dev board now reflects true urgency without manual updates.
Trigger
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.
Action
Edit Issue
Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.
Why this helps
A blocker gets tagged in Asana but devs don't see it in Jira where they're actually working. The urgency gets lost and the issue doesn't get the attention it needs.
- Urgent work gets attention where it matters—in Jira
- Eliminate manual priority updates across two tools
- Tag once, propagate priority everywhere
- Make sure blockers stay visible and don't slip through
Setup
Build it in a few focused steps.
- 1Connect Asana and Jira to Notis (one-time integration).
- 2Tell Notis your tag-to-priority mapping: 'When urgent tag is added to an Asana task, set Jira priority to High. When blocker is added, set it to Critical.' or equivalent.
- 3Choose 'Tag Added to Task' as the trigger and select your notification channel.
- 4Test by adding a tag to an Asana task and watch the priority update in Jira instantly.
Questions about this workflow
Can I use multiple tags to set different priorities?
Yes. You can define a mapping: urgent→High, blocker→Critical, nice-to-have→Low, etc. Notis applies the correct priority based on the tag.
What if a task gets a tag added but I want to remove the priority flag later?
You can set a second automation: 'Remove the urgent tag, and set Jira priority back to Normal.' Notis handles tag removal too.
Do both tools need to have the same tag names?
No. You can map Asana tags to any Jira priority. E.g., Asana's 'critical' can map to Jira's 'Highest' even if the names differ.
Can this work with custom fields instead of priority?
Yes. Prompt Notis: 'Add a tag to an Asana task and set a custom Jira field.' Notis adapts to your workflow.
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.