Skip to content
Notis

Keep Jira coverage plans current when PTO changes

When time-away details shift, update the existing coverage issue so the team's plan reflects the latest context.

Trigger

Webhook received

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

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

A changed absence can make a carefully planned Jira handoff stale unless someone updates it.

  • Keep an existing coverage issue aligned with updated absence context.
  • Reduce confusion from stale dates or handoff notes.
  • Make changes visible in Jira where the plan is tracked.

Setup

Build it in a few focused steps.

  • 1Connect BambooHR and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name.
  • 3In one instruction, tell Notis to update the specified Jira coverage issue with the changed PTO details included in the request.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one real changed-PTO example and confirm the issue reflects the new plan.

Questions about this workflow

How does Notis find the coverage issue?

Include its Jira key or identifier in the incoming request. The BambooHR description does not specify a Jira linkage.

Will it detect changed PTO on its own?

No BambooHR trigger events are listed. An HTTP request starts the workflow, and that request should carry the updated PTO context.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Bamboohr 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.

Bamboohr 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.