Back to Changelog
Back to Changelog

September 12, 2024

On-Call

🤑 On-Call Pay Calculator

🤑 On-Call Pay Calculator

Compensating incident responders fairly can be a complex task, especially when your on-call management tool and payroll platform don’t talk to each other. You’re stuck tracking on-call hours manually and verifying that responders did in fact work those scheduled hours (last minute overrides, anyone?), crunching the numbers and getting them over to payroll. With that amount of overhead, it’s no wonder many companies don’t reliably compensate for on-call hours. 

Luckily for Rootly On-call users, we’ve made on-call payroll simple with the ability to generate On-Call Pay Reports right from Rootly. You can configure hourly or daily pay rates for on-call hours and we’ll create timesheets detailing the total hours and owed pay in the currency of your choice for all responders during that period, based on your specified pay rate. We also track which on-call shifts took place on holidays or weekends so it’s easy to adjust rates accordingly.

These reports auto-update as well, so you can even re-generate previous reports based on any changes made after the time period. On-call pay reports can be easily exported from the Rootly web platform as a .CSV or .XLSX file to import into other tools.

Find On-Call Pay Reports in the Rootly web navigation under the On-Call tab. It takes just seconds to configure your pay rules, and you’re ready to start generating reports for any time period right away.

🌝 New & Improved

🆕 Introduced separate Schedule Override Permissions to allow Rootly On-Call users to be scoped to create/edit overrides, but create/edit full schedules.

🆕 Introduced new {{ incident.group }} option for setting the Service field in PagerDuty workflow actions. Now teams that have linked Rootly Teams to PagerDuty Services can use this option to dynamically reference the first Team selected for an incident.

💅 Improved retrospective step notifications to avoid weekends. “Before due date” and “After due date” notifications will be sent either before or after the weekend, should the configured notification schedule fall on a weekend.

💅 Added modal to warn the end user when attempting to delete a User that’s still a member of a Team. This will help ensure all members of a Team are also members of the Organization.

💅 Implemented additional enforcement of what field type can be mapped as Alert Title for Generic Webhooks. Now, only string fields can be mapped as alert titles.

🐛 Fixed display issue with services/teams that contain long names not wrapping on Alert Details pages.

🐛 Fixed inability to resizing the Summary field on web UI when rich text format is used.

Previous post
Previous post
You are viewing the latest post

Update Custom Incident Fields Using Workflows

🤖 Ask Rootly AI (+ More New AI Features!)

Rootly AI Editor: Fix Typos, Grammatical Errors, and Wordy Text Instantly

📊 Dashboard Sharing Permissions

✍️ Customize Your Wordbank for Automatic Incident Title Generation

🧠 Smart Defaults for Jira

🔌 The Rootly Plugin for Zendesk

🪄 Rootly Retrospectives

⚡ Command Palette: Lightning Fast Navigation with a Single Keyboard Command

Rootly Terraformer: Seamlessly Bring Workflows From Rootly’s UI to Terraform

Smart Defaults for Slack Configuration

Rootly Rewind: Celebrating 2023 With Our Amazing Customers!

Search and Filter Available Actions for Workflows

Incident Timeline Comments: Add Context and Move from Conversation to Action Seamlessly

Introducing: Rootly x ClickUp! Our New Integration for Seamless Collaboration and Task-Tracking

The New and Improved Home Dashboard

Guided Onboarding Flow for New Rootly Users

Fields List View and More UX Improvements for Forms & Form Fields

Bulk Actions for Incidents and Workflows

Share and Set Permissions for Rootly Metrics Dashboards

Bulk Edit Task and Follow-up Action Items

Create Fully Custom Slack Forms Using Our New Form Builder

Specify Public vs Internal Incident Titles on Your Rootly Status Pages

Integrate with Multiple Instances of Jira and Confluence

Auto map any user from PagerDuty and Jira to Rootly incidents with new user lookup