Skip to content
Notis

Make issue reproduction steps easier to gather

Start a Coda reproduction page with each new Jira issue, so testers have a clear place to capture steps and findings.

Trigger

New Issue

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

Action

Create a page

Create a new page in a doc. note that creating a page requires you to be a doc maker in the applicable workspace.

Why this helps

Reproduction details are often missing or split across messages, slowing down issue investigation.

  • Keep reproduction steps near the issue context.
  • Make missing investigation details visible.
  • Give contributors one place to add findings.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Coda once in the Notis portal.
  • 2Create an automation from Automations, New Automation, and give it a name.
  • 3Tell Notis to create a Coda reproduction page for each new issue with available Jira details and sections for steps, environment, and findings.
  • 4Pick the Jira New Issue trigger and choose where run reports should go.
  • 5Test with one real issue and check the page before using it for active investigations.

Questions about this workflow

Does Jira always provide reproduction details?

No. The page can include available Jira details and sections for people to fill in missing information.

Which issues trigger the page?

Only issues created in the configured Jira project trigger this automation.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to Coda. A trigger fires from one place; an action lands in another.

Jira triggers

Coda actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Add a category for pack

Add a publishing category for a given pack.

ActionInstant

Webhook trigger

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

TriggerInstant

Add a maker for pack

Set a maker for a given pack. used to display makers for a pack in the corresponding packs page.

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

Add a permission for pack

Create or modify user, workspace, or global permissions for a given pack.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Add custom domain

Add a custom domain to a published doc.

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

Add permission

Adds a new permission to the doc.

ActionInstant

Begin content export

Initiate an export of content for the given page.

ActionInstant

Content export status

Check the status of a page content export

ActionInstant

Copy Document

Creates a copy of an existing coda document. this action allows you to duplicate a document while optionally specifying a new title and location for the copied document.

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Coda, 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 Coda.