Keep opportunity stage in sync with delivery progress
An issue moving through Jira (Backlog -> In Progress -> In Review -> Done) reflects delivery progress. Notis automatically syncs that to the opportunity stage in Salesforce, so your forecast stage always matches reality.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Get opportunity
Retrieves a specific opportunity by id from salesforce, returning all available fields.
Why this helps
Issues progress through Jira while opportunities sit stale in the same stage in Salesforce. Your forecast doesn't reflect actual delivery progress, so forecasting accuracy suffers.
- Accurate forecast: opportunity stage matches delivery progress
- Real-time insight: sales always sees the true delivery status
- No stale deals: stages move as work moves
- Better decisions: forecasts are based on actual progress, not guesses
Setup
Build it in a few focused steps.
- 1Connect Jira and Salesforce to Notis.
- 2Tell Notis: "Map Jira statuses to Salesforce opportunity stages: Backlog -> Prospecting, In Progress -> Qualification, In Review -> Needs Analysis, Done -> Closed Won." Set the trigger to Updated Issue (monitoring status changes).
- 3Define the exact mappings for your workflow.
- 4Choose your notification channel.
- 5Test by moving an issue through Jira and confirming the opportunity stage updates in Salesforce.
Questions about this workflow
What if my Jira and Salesforce stages don't align perfectly?
Tell Notis your custom mapping. You control how each Jira status translates to a Salesforce stage.
Should the opportunity close automatically when the issue is done?
You decide. You might say, "Move to Closed Won when the issue is done" or "wait for manual confirmation." Your rule.
What if multiple issues map to one opportunity?
Notis can track that. You might say, "Update the opportunity to In Progress if any related issue is being worked." It uses logic, not just 1:1 mapping.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Salesforce. A trigger fires from one place; an action lands in another.
Jira triggers
Salesforce actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create Salesforce Account
Deprecated: creates a new salesforce account using a json post request, requiring 'name'; specific fields (e.g., custom, dunsnumber) may have org-level prerequisites.
New Project
Triggered when a new project is added in Jira
Add contact to campaign
Adds a contact to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Add lead to campaign
Adds a lead to a campaign by creating a campaignmember record, allowing you to track campaign engagement.
Add product to opportunity
Adds a product (line item) to an opportunity. the product must exist in a pricebook entry that's associated with the opportunity's pricebook.
Apply lead assignment rules
Applies configured lead assignment rules to a specific lead, automatically routing it to the appropriate owner based on your organization's rules.
Associate contact to account
Associates a contact with an account by updating the contact's accountid field.
Clone opportunity with products
Clones an opportunity and optionally its products (line items). creates a new opportunity with the same field values and products as the original.
Clone record
Creates a copy of an existing salesforce record by reading its data, removing system fields, and creating a new record. optionally apply field updates to the clone.
Connect any two apps with Notis in the middle.
Not just Jira and Salesforce. 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 Salesforce.