Does your team use Conventional Commits? We reward you handsomely for doing so. DoubleLoop generates your changelog automatically based on data you already have in GitHub. We parse your commit messages to clean up the names and adds labels such as "Feature" or "Fix." For each week, we highlight the features and summarize all the other updates in a bulleted list below.
When you inform users of a new feature, give them a clear next step by prompting folks to "See the demo!", "Read the docs!", or "See it action!" Name the call-to-action however you want and point it to any URL.
Sometimes a feature or fix is worth mentioning to your customers, but it doesn't require a prominent treatment. Now, you can share a list of "Minor updates" for each week in your changelog.
DoubleLoop now sends automated digest emails. It's a great way to stay on top of launch activity at your company or share updates with your customers.
Until today, you could use DoubleLoop to build an internal changelog for your company. Now, you can use DoubleLoop to build public changelogs to share directly with your customers, stakeholders, or investors. This page is an example!
If your team references the Jira or Clubhouse Id in pull requests or commits, it now appears as "related work" in your internal changelog. For engineers, it helps you understand the business context of code changes. For product managers, it helps you understand the effort involved with each product change.
Thanks to our new Zapier integration, you can now add events to your internal changelog when you, for example, send a newsletter via Hubspot or Tweet. Coupled with our Google analytics integration, it's a powerful way to show the impact of your marketing initiatives.
At DoubleLoop, we use Clubhouse, an alternative to Jira. You can now automatically build your internal changelog based on Clubhouse data. For example, we created a "view" of our completed feature stories. It makes it super fast to curate this public changelog.
We've invested a lot in capturing valuable info about the product change events that we import from your tools. You can now see more of this info in the Slack notifications.
Our metrics graph just way more useful.
Find everything that a person contributed, searching across multiple tools at once.
Automatically build your internal changelog with Jira data. Create filtered views, connect them to slack, and share with stakeholders or customers.
Use DoubleLoop to send the right notifications to the right people. For example, send a message everytime code gets pushed to production or when I feature is marked as completed. Or curate a stream of only the big product launches.
We filter out the noise from bot code merges (like dependabot) so you can focus on the product changes that matter.
Build a timeline of your product with GitHub data.
When you ship something, record it!