Skip to content
Notis

Start a Python analysis workspace for each new Jira project

Give a new project a ready place for scripts and analysis as soon as it is created.

Trigger

New Project

Triggered when a new project is added in Jira

Action

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.

Why this helps

Project setup often leaves the analysis environment as one more thing someone has to remember to create.

  • Create a sandbox when a Jira project is added.
  • Reduce manual setup before project analysis begins.
  • Use the sandbox for Python scripts, files, and outputs.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Codeinterpreter once in the Notis portal.
  • 2Create an automation named Create a project analysis workspace, in the portal or from any Notis channel.
  • 3Tell Notis to create a Codeinterpreter sandbox when a new Jira project is added and report how to access it.
  • 4Pick Jira New Project as the trigger and choose where run reports should go.
  • 5Test with one real new project event.

Questions about this workflow

Will it populate the workspace with project data?

This workflow creates a sandbox. It does not fetch Jira project data unless you separately specify available data and an action that supports it.

What is the sandbox for?

It is a cloud environment for running Python code, reading and writing files, and reviewing outputs.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Get File

Get a file from the sandbox and returns the file. the files should be read from /home/user folder.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

Upload File

Upload a file to the sandbox environment. the files should be uploaded to the /home/user folder.

ActionInstant

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.