Apply your priority rubric when Jira issues change
Keep triage decisions consistent when issue details change, with the relevant evidence and reasoning in one report.
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
Execute Code
Execute python code in a sandbox and return any result, stdout, stderr, and error. use /home/user folder to write/read files. try to not use plt.show() as the code is executed remotely. use files for image/chart output instead.
Why this helps
A change to an issue can make an old triage decision stale, but checking every edit manually takes focus.
- Reapply your written rubric when an issue changes.
- Show which supplied issue details informed the recommendation.
- Make unclear or missing inputs visible.
Setup
Build it in a few focused steps.
- 1Connect Jira and Codeinterpreter once in the Notis portal.
- 2Create an automation named Triage updated Jira issues, in the portal or from any Notis channel.
- 3Tell Notis to evaluate each updated issue against your supplied priority rubric and report the recommendation, evidence, and missing inputs.
- 4Pick Jira Updated Issue as the trigger and choose where run reports should go.
- 5Test with one real issue update and review the recommendation.
Questions about this workflow
Can it use business impact that is not recorded in Jira?
Only if you provide that information. The workflow should identify missing context rather than assume it.
Will it change Jira priority?
No. The selected Codeinterpreter action runs analysis and returns a report; it does not update Jira.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Codeinterpreter. A trigger fires from one place; an action lands in another.
Jira triggers
Codeinterpreter actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Sandbox
Create a sandbox to execute python code in a jupyter notebook cell. this is useful for agents to communicate, execute code, see output, read files, write files, etc. it's like you own personal computer, but in the cloud. use /home/user folder to write/read files.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Execute Code
Execute python code in a sandbox and return any result, stdout, stderr, and error. use /home/user folder to write/read files. try to not use plt.show() as the code is executed remotely. use files for image/chart output instead.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Get File
Get a file from the sandbox and returns the file. the files should be read from /home/user folder.
New Project
Triggered when a new project is added in Jira
Run Terminal Command
Run a command in the terminal and returns the stdout, stderr, and error code. use /home/user folder to write/read files.
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.
Upload File
Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.
Connect any two apps with Notis in the middle.
Jira and Codeinterpreter, 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 Codeinterpreter.