Convert Customer Requests to Jira Issues
A customer submits a support request through your portal. Notis receives the webhook and creates a Jira issue within seconds, with all details and priority pre-set.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Why this helps
Customer feedback arrives through support channels or feedback forms but doesn't make it into your dev backlog. Requests get lost or forgotten.
- Centralize all customer feedback in Jira for prioritization
- Reduce response time from request to issue creation
- Prevent feedback from getting lost or forgotten
- Enable product team to act on customer input immediately
Setup
Build it in a few focused steps.
- 1Connect Jira to Notis and get a webhook URL.
- 2Configure your customer support or feedback system to POST requests to the webhook URL Notis provides.
- 3Tell Notis: 'When a customer request webhook arrives, create a Jira issue with priority based on the customer tier or issue type.' Notis maps the data.
- 4Send a test request and verify the Jira issue appears.
Questions about this workflow
What if the webhook payload has custom fields?
Notis adapts. Include the custom data in your prompt and Notis maps it to Jira fields or creates custom fields as needed.
Can I set different priorities based on the customer or issue type?
Yes. Define rules: 'If customer tier is gold, set priority to High. If it's a bug, set to Critical.' Notis applies the logic.
How do I know if a webhook was received and processed?
Notis sends a confirmation to your notification channel. You can also check Jira to see the created issue.
Can this link the webhook request to existing Jira issues?
Yes. If the request mentions an issue number or key, Notis can link to that issue or mark it as a duplicate.
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
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Attachment Added to Task
Triggers when an attachment is added to a task.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
New Comment on Task
Triggers when a comment is added to a task in a project.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
New Task Created
Triggers when a new task is created in a project.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Task Moved to Section
Triggers when a task is moved to a section in a project.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
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.
Link Issues
Links two jira issues using a specified link type with optional comment.
Task Updated
Triggers when a task is updated in a project.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Asana and Jira, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Jira.