Auto-Resolve Jira When Asana Task is Done
Your team finishes work in Asana and marks a task complete. The Jira issue automatically transitions to Done, keeping your burn-down accurate.
Trigger
Task Updated
Triggers when a task is updated in a project.
Action
Transition Issue
Transitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.
Why this helps
Asana tasks get marked done but Jira issues stay open. Your burn-down metrics are unreliable and the team's work goes uncredited.
- Keep accurate metrics in Jira without manual status updates
- Ensure completed work is immediately marked as done
- Reduce manual workflow state management
- Maintain reliable burn-down and sprint forecasting
Setup
Build it in a few focused steps.
- 1Set up both integrations in Notis.
- 2Tell Notis: 'When a task is marked complete in Asana, transition the Jira issue to Done (or Resolved if using a different workflow state).' Notis learns your workflow states.
- 3Set trigger to 'Task Updated' and filter for completion status, or select the relevant section if Asana uses sections. Choose your notification channel.
- 4Mark an Asana task as complete and verify the Jira issue transitions automatically.
Questions about this workflow
What if Jira's workflow doesn't have a Done state?
Notis uses the appropriate terminal state in your workflow (e.g., Closed, Resolved, Shipped). You can specify which in your prompt.
Can I add a comment or note when completing?
Yes. Refine your prompt: 'When the task is marked complete, transition the Jira issue and add a comment: Completed in Asana on [date].' Notis handles both.
What if I un-mark a task as complete—does Jira reopen?
You can configure this: 'If moved back to in-progress, reopen the Jira issue' or 'Leave it closed regardless.' You choose the behavior.
Does this affect time tracking or worklogs?
This only changes the issue state. Worklogs and time tracking remain independent unless you set up separate automations.
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 1,000+ 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.