Skip to content
Notis

Keep Jira issue details current with Basecamp briefs

A regular review can catch tickets whose descriptions no longer match the latest project brief.

Trigger

Recurring schedule

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

Action

Edit Issue

Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.

Why this helps

Jira descriptions become stale as plans evolve in Basecamp, creating avoidable clarification and rework.

  • Catch clear differences between plans and tickets.
  • Reduce rework caused by stale issue details.
  • Keep Jira focused on the current project direction.

Setup

Build it in a few focused steps.

  • 1Connect Basecamp and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3In one instruction, ask Notis to compare current briefs with referenced Jira issues and update only details that are clearly outdated.
  • 4Choose a recurring schedule and a channel for run reports.
  • 5Test with one real brief and inspect the issue changes.

Questions about this workflow

Can it determine which brief maps to each issue?

Provide issue keys in the brief or reliable references in your instruction. Without a clear match, ask Notis to report the ambiguity.

Does it replace the Jira description every time?

Tell Notis to update only when a substantive change is clear and retain details that remain accurate.

What if the latest brief is not available to Notis?

Supply the current brief in the information available to the automation. The workflow cannot compare against material it cannot access.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Basecamp triggers

Jira actions

Recurring trigger

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

TriggerScheduled

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

Connect any two apps with Notis in the middle.

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