Skip to content
Notis

Keep Jira work moving when an employee exits

When an exit affects active work, transition the identified Jira issue so the team's next step is clear.

Trigger

Webhook received

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

Action

Transition Issue

Transitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.

Why this helps

Work can stay in the wrong Jira state when an employee leaves and nobody updates the issue workflow.

  • Reflect a known work transition in the Jira issue state.
  • Keep the issue workflow aligned with the handoff context.
  • Reduce manual follow-up to find and update affected work.

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.
  • 3Tell Notis in one instruction which identified Jira issue to transition and the intended state based on the supplied exit context.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one real issue and verify the available transition and resulting state.

Questions about this workflow

Can an employee exit tell Notis which issue to transition?

Only if the incoming request includes the relevant Jira issue identifier and the intended workflow outcome. BambooHR does not provide Jira issue relationships in the source description.

What if Jira does not allow that transition?

The transition must be available for the issue's current workflow state and permitted for the connected Jira user. Review the run report and Jira permissions if it fails.

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.