Released

1
5 0 Reviews 1 Saved
Introduction: Released is a product communication platform that converts Jira tickets into shareable roadmaps and release notes. It serves as a central hub for product teams to keep stakeholders and customers informed. Key features include tailored roadmaps, AI-generated release notes, feedback collection, and product portals that aggregate cross-project Jira data, all while maintaining Atlassian security and user management standards.
Monthly Visitors: 8.6K

Released Product Information

What is Released?

Released is a product communication platform designed to transform Jira tickets into shareable roadmaps and release notes. It helps product teams keep customers and stakeholders in the loop by creating a central hub for product communication. With Released, users can share Jira roadmaps, publish release notes, collect feedback, and create product portals with cross-project roadmaps from Jira. The platform offers features like tailored roadmaps, AI-powered release notes, and direct feedback collection, all seamlessly integrated with Atlassian user management and security practices.

How to use Released?

Released connects to your Jira instance, allowing you to transform internal Jira Product Discovery roadmaps into dynamic portals. You can customize views, share roadmaps and release notes, and collect feedback. Users can authenticate via Atlassian ID, Google, or email verification to access restricted portals. The portal can be hosted on a custom domain or embedded directly within your website or app.

Released's Core Features

  • Share Jira roadmaps
  • Publish release notes
  • Collect feedback in one place
  • Create product portals with cross-project roadmaps from Jira
  • AI-powered release notes generation
  • Customizable portals with branding options
  • User authentication via Atlassian ID, Google, or email
  • Integration with Atlassian user management and security practices

Released Use Cases

#1 Share tailored roadmaps with customers and stakeholders
#2 Publish engaging release notes automatically generated from Jira tickets
#3 Collect user feedback directly to your inbox
#4 Communicate product updates to both internal and external audiences
#5 Create dedicated portals for Jira Product Discovery

FAQ from Released

Does Released require a Jira license? +

No, users can access restricted portals by authenticating via Atlassian ID, Google, or email verification without needing a Jira license.

Is Released secure? +

Yes, Released is SOC 2 Type 2 certified and integrates with Atlassian user management and security protocols. All data is encrypted both in transit and at rest.

Can I customize the look and feel of my product portal? +

Yes, you can customize the portal's appearance by adding your company logo and brand colors.

Can I use my own domain for the product portal? +

Yes, you can host your portal on a custom domain or embed it directly into your website or application.

How does Released help with writing release notes? +

Released features an AI copywriter that generates release notes from Jira tickets, allowing you to create content up to 10x faster. You can also adjust the AI settings to match your brand's tone of voice.

Released Pricing

Free

$0

Free plan available.

Related Model Comparison Pages

Use these comparison pages to understand the trade-offs between the models most relevant to Released.

Compare Gemini 1.0 Pro Deprecated and Gemini 2.0 Flash across pricing, context window, capabilities, benchmarks, and API access to choose the better fit for long-context workloads versus long-context workloads.

Compare Gemini 1.0 Pro Deprecated and Gemini 2.5 Flash across pricing, context window, capabilities, benchmarks, and API access to choose the better fit for long-context workloads versus long-context workloads.

Compare Gemini 2.0 Flash Lite and Gemini 2.0 Flash across pricing, context window, capabilities, benchmarks, and API access to choose the better fit for long-context workloads versus long-context workloads.

Compare Gemini 2.5 Flash and Gemini 2.0 Flash across pricing, context window, capabilities, benchmarks, and API access to choose the better fit for long-context workloads versus long-context workloads.