Add Timezone Context to Your Jira Workflow
When a new issue lands in Jira, Notis captures the current time in your timezone so deadline estimates and calendar scheduling are never miscalculated.
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
Get current date and time
Gets the current date and time, allowing for a specific timezone offset.
Why this helps
Neurodivergent founders working across timezones or with distributed teams often misestimate deadlines because they lose track of the current time or timezone context.
- Ensure deadline calculations are always timezone-aware
- Prevent miscalculations from UTC confusion or timezone assumptions
- Add time context to every issue for accurate planning
- Support distributed teams with automatic timezone handling
Setup
Build it in a few focused steps.
- 1Connect Jira in Notis Integrations.
- 2Create an automation: 'When a new Jira issue is created, capture the current time in my timezone [e.g., EST/PST] as context.'
- 3Set the trigger to 'New Issue' and choose your Jira project.
- 4Specify your timezone in the automation prompt.
- 5Test by creating a Jira issue and note the timezone context in the run confirmation.
Questions about this workflow
Does this change the calendar event times?
Not directly. This captures timezone context in the automation run log. Use it alongside other automations to ensure accurate calendar event times.
Can I support multiple timezones?
Yes. Set up separate automations for different team timezones, or use a 'world clock' format to capture multiple zones in one run.
Will this help with deadline calculations?
Yes. By capturing current time in your timezone, Notis can accurately calculate deadlines relative to when the issue was created.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Google Calendar. A trigger fires from one place; an action lands in another.
Jira triggers
Google Calendar actions
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Insert Calendar into List
Inserts an existing calendar into the user's calendar list.
New Project
Triggered when a new project is added in Jira
Update Calendar List Entry
Updates an existing entry on the user\'s calendar list.
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.
Delete Calendar
Deletes a secondary calendar. use calendars.clear for clearing all events on primary calendars.
Update Calendar
Updates metadata for a calendar.
Clear Calendar
Clears a primary calendar. this operation deletes all events associated with the primary calendar of an account.
Create Event
Creates an event on a google calendar, needing rfc3339 utc start/end times (end after start) and write access to the calendar. by default, adds the organizer as an attendee unless exclude organizer is set to true.
Delete event
Deletes a specified event by `event id` from a google calendar (`calendar id`); this action is idempotent and raises a 404 error if the event is not found.
Create a calendar
Creates a new, empty google calendar with the specified title (summary).
Connect any two apps with Notis in the middle.
Not just Jira and Google Calendar. Any combination from 985+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Google Calendar.