Enhanced Incident Time Management, Better Jira Cloud Integration Management

Hey there, Firefighters 🧑‍🚒 Here’s what’s shipped for you this week:

⏰ Improved Incident Time Management

We’ve made it easier to track time during incidents — whether you’re working across time zones or managing shift changes.

What does this mean for you?

• Clearer time zones: Now you can easily switch between UTC and local time in Milestone forms, so everyone stays on the same page, no matter where they are.
• More precise shift timing: Shift cards now show exact minutes instead of rounded hours, so you always know when your shift starts and ends.
• Better calendar experience: The "My Shifts" filter now works as expected, making it easier to see your upcoming shifts.

🔁 Jira Cloud Integration: Easily Manage Multiple Instances

Use multiple Jira Cloud instances within FireHydrant? This one’s for you. You can now add display names, so it’s easier to identify and manage multiple Jira instances within your organization.

⚒️ Other Improvements

• Microsoft Teams integration: We’ve made user management more robust, preventing issues with bot users and duplicate participants in group chats.
• Better user visibility in Incidents & Retrospectives: Now, you’ll always see the avatars of people currently viewing the page (not just after in the post-resolved state), plus cleaner placement of incident details for better readability.

🐛 Bug Fixes

• We’ve fixed an issue where organization settings couldn’t be saved if a logo had not yet been added to the org.
• Resolved an error that sometimes prevented users from seeing role changes in the Incident Timeline.
• Stopped the Follow-Up form from crashing when selecting certain projects. The form now gracefully handles invalid project selections and provides clear error messages to users.
• Fixed a bug that sometimes caused severity suggestions not to load.
• Some users using Safari were getting errors on Incident and Retrospectives pages. That’s fixed!
• Fixed an issue where changing the time while requesting shift coverage caused an error.