Carry complete incident updates into CommCare
When incident details are ready, submit the supplied CommCare form from the Jira update and keep the handoff easy to track.
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
Submit Form to CommCare
Tool to submit an XForm to CommCare following the OpenRosa standard. Use when you need to submit form data with complete XML including required metadata fields (deviceID, timeStart, timeEnd, username, userID, instanceID).
Why this helps
Incident information may be updated in Jira but still need manual transfer into CommCare, increasing delay and re-entry effort.
- Reduce re-entry for complete incident submissions.
- Use the updated issue as the trigger for a ready-to-submit form.
- Surface incomplete payloads in the run report rather than submitting guesses.
Setup
Build it in a few focused steps.
- 1Connect Jira and CommCare once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3In one instruction, ask Notis to submit the supplied incident XForm only when the Jira issue includes the full XML and required metadata.
- 4Pick Jira Updated Issue as the trigger and choose where run reports go.
- 5Test with one real updated issue containing a valid example payload.
Questions about this workflow
Can the workflow fill in missing incident XML?
The action requires an XForm submission. Provide the complete form content and required metadata in the issue or an approved source.
Which metadata is required?
The standard submission requires deviceID, timeStart, timeEnd, username, userID, and instanceID, along with the complete XML.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to CommCare. A trigger fires from one place; an action lands in another.
Jira triggers
CommCare actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Lookup Table
Tool to create a new lookup table in a CommCare domain. Use when you need to set up reference data structures like product catalogs, price lists, or configuration tables. Requires 'Edit Apps' permission.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Web User Invitation
Tool to create an invitation for a new web user in CommCare. Use when you need to invite a user with specific role and permissions. Requires 'Edit Web Users & Edit Access API' permissions.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List Reports
Tool to retrieve available reports configured in a CommCare project. Use when you need to discover what reports exist before downloading report data via the Download Report Data API.
New Project
Triggered when a new project is added in Jira
Single Sign On
Tool to validate login credentials and retrieve user profile for a mobile worker or web user. Use when you need to authenticate a user and obtain their profile information including roles, permissions, locations, and configuration details.
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.
Submit Form to CommCare
Tool to submit an XForm to CommCare following the OpenRosa standard. Use when you need to submit form data with complete XML including required metadata fields (deviceID, timeStart, timeEnd, username, userID, instanceID).
Submit Form ODK Compatible
Tool to submit form data using ODK-compatible endpoint for Android client compatibility. Use when submitting XForm data to CommCare. Requires properly formatted XML with metadata including unique instanceID.
Connect any two apps with Notis in the middle.
Jira and CommCare, 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 CommCare.