Auto-Create Jira Version from Asana Spec Attachments
A designer uploads a spec labeled 'v2.1-design' to Asana, and Notis creates a matching version in Jira. Releases track themselves.
Trigger
Attachment Added to Task
Triggers when an attachment is added to a task.
Action
Create Version
Creates a new version for releases or milestones in a jira project.
Why this helps
Specs and design files arrive in Asana but Jira versions stay unmaintained. There's no connection between the design iteration and the release it belongs to.
- Link design specs to release versions automatically
- Maintain accurate version history tied to specs
- Reduce manual version management in Jira
- Improve traceability from design to release
Setup
Build it in a few focused steps.
- 1Connect Asana and Jira to Notis.
- 2Tell Notis: 'When a file with version info (e.g., v2.1) is attached to an Asana task, create a matching version in Jira.' Notis extracts version numbers from filenames.
- 3Set trigger to 'Attachment Added to Task' and select your notification channel.
- 4Attach a test file with version info (e.g., 'design-v2.1.pdf') and confirm Jira creates the version.
Questions about this workflow
How does Notis extract version numbers from file names?
It looks for patterns like v1.0, v2.1, 2.1, release-3.0, etc. You can refine the pattern in your prompt if needed.
What if the version already exists in Jira?
Notis checks first and won't create duplicates. It will notify you if the version exists.
Can I link the version to specific issues or projects?
Yes. Refine your prompt: 'Create the version in the frontend project' or 'Link it to issues tagged with this sprint.' Notis applies the context.
Can I set start/end dates for the version automatically?
You can set rules: 'If version is labeled release-soon, set end date to 2 weeks from today.' Notis applies date logic based on patterns.
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.