August 2025 Product Update: Multi-file Specs, Better Jira Integration, and Workflow Fixes
We’ve shipped some improvements this month to make your workflows a little smoother. Multi-file specs now work in Spec Hub, Jira integration is ready to handle enterprise setups, and we added a few quality-of-life improvements that should save you some clicks.
Build robust APIs with multi-file spec support
Complex APIs often span multiple files, but many tools force you into single-file constraints that don’t match how real APIs are built. That means you’re manually managing references across separate files, hunting for validation errors buried in different contexts, or getting lost trying to navigate a single unwieldy spec file. Documentation generation breaks down when your spec doesn’t fit the tool’s assumptions, and you struggle to maintain API consistency across teams without slowing down development with review bottlenecks.
Spec Hub now supports multi-file specifications for OpenAPI 3.0, letting you organize complex APIs more intuitively and focus on smaller chunks at a time. Add, delete, and rename files within your specification while Spec Hub automatically maintains all references and relationships. Spec Hub’s unified validation identifies issues across all files to make sure live documentation previews and collection generation run seamlessly, regardless of file structure. Custom governance rules let organizations define standards that are enforced automatically as developers work without the friction of manual checks.
Create detailed Jira issues without the workflow disruption
When API requests don’t perform the way you expect, manually logging issues becomes a frustrating detour. You’re copying request details by hand, figuring out which Jira instance to use, and trying to populate custom fields while the context of what went wrong fades from your memory. Custom Jira setups make this even more challenging with multiple instances and specific field requirements that turn simple bug reporting into a multi-step process.
The Postman Jira integration now supports multiple Jira instances and custom/required fields, letting you create detailed issues directly from requests. The integration automatically includes request URLs and response payloads while displaying your organization’s specific field requirements, so the teammate assigned to the issue has all the context they need to reproduce and fix it fast.
Collaborate on Postman Notebooks with comments and reactions
You find lots of great API projects and tutorials on the Postman API Network, but when you want to give feedback to creators, there’s no straightforward way to do it. You might have questions about implementation details, suggestions for improvements, or just want to acknowledge their clever solutions. This communication gap makes it harder for creators to improve their content and for the community to build on each other’s work.
Postman Notebooks now include comments and reactions, giving you a direct way to communicate with creators and collaborate on API projects:
-
Comment on any section to ask questions, suggest improvements, or share your experience
-
Use reactions to quickly show appreciation for helpful content
-
Create a feedback loop that helps creators refine their projects
Try it out with your own entry in the Postman Notebook Challenge, where your creativity can meet community.
Additional improvements
We’ve also added some workflow enhancements to help streamline daily collaboration:
-
View counts on collections help you understand API usage patterns. Catch the replay of our recent Beyond the Build livestream for a quick demo (you’ll see multi-file specs in Spec Hub in this episode, too!)
-
Improved comment discoverability makes it easier to find and engage with team feedback inside workspaces. Comments are now more visible and accessible, making it possible to build workflows around team discussions and feedback loops.
-
Comments on collection runs allow you to discuss test results without switching tools (see them in action in this Beyond the Build replay). You can now add comments to Collection Run reports and see testing stats in monitors and scheduled runs, so you can track issues and collaborate right where the data lives.
Wrapping up
That’s what’s new this month at Postman: better spec management, simplified issue reporting, and improved team collaboration. Head over to our community to see what others are saying about this month’s updates. Our team loves hearing from you, and your feedback shapes what we build next.
Keep it 200,
The Postman Team

What do you think about this topic? Tell us in a comment below.