Skip to content
Notis

Keep Control D schedules current with Jira changes

When an approved access window changes, update the schedule tied to its Jira request.

Trigger

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.

Action

Update Profile Schedule

Tool to update a specific schedule within a profile. Use when you need to modify schedule details after confirming profile_id and schedule_id.

Why this helps

Changed access timing can leave an outdated schedule active when ticket updates do not reach the profile.

  • Carry approved timing changes into an existing schedule
  • Reduce the risk of stale access windows
  • Require profile and schedule identity before updating

Setup

Build it in a few focused steps.

  • 1Connect Jira and Control D once in the Notis portal.
  • 2Create an automation in the portal or tell Notis from any channel to create one.
  • 3In one instruction, ask Notis to update only the identified Control D schedule for an approved Jira timing change, and clarify missing profile or schedule details.
  • 4Pick the Jira Updated Issue trigger for the configured project and choose where run reports should go.
  • 5Test with one real schedule change and verify the updated timing.

Questions about this workflow

What identifies the schedule to update?

The request should identify the Control D profile and schedule, along with the approved new timing details. Have Notis ask when either identifier is uncertain.

Will ordinary Jira edits change the schedule?

The trigger fires on issue changes, so your instruction should limit action to approved schedule changes with explicit new timing.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Jira triggers

Control d actions

Recurring trigger

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

TriggerScheduled

Delete Device by ID

Tool to delete a Control-D device. Use when you need to remove a device by its identifier after confirming the device_id.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete Profile by ID

Tool to delete a profile. Use when you need to remove a profile by its ID after ensuring it is not enforced by any device.

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

Delete Profile Rule by Hostname

Tool to delete a specific custom rule by hostname from a profile. Use after confirming profile_id and hostname.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Delete Profile Rule by Rule ID

Tool to delete a specific custom rule by its ID within a profile. Use after confirming profile_id and rule_id.

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

Delete Profile Rule in Folder

Tool to delete a specific custom rule within a folder. Use after confirming profile_id, rule_id, and folder_id.

ActionInstant

Delete Profile Schedule

Tool to delete a specific schedule within a profile. Use after confirming profile_id and schedule_id.

ActionInstant

List Known Access IPs

Tool to list known IPs associated with the account. Use when you need to retrieve recent access IPs for device resolver queries.

ActionInstant

Get Analytics Endpoints

Tool to list analytics storage regions and their endpoints. Use after authenticating to retrieve available analytics regions.

ActionInstant

Connect any two apps with Notis in the middle.

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