If your team does not use traditional version-based releases, tracking frequent updates can become difficult. This video shows how to create release notes from Jira without creating formal versions, using custom variables to automatically capture relevant changes based on date or creation window. It makes Jira release notes more flexible, accurate, and aligned with actual delivery cycles.
At Amoeboids, we simplify the process if you prefer creating a release in Jira or avoiding it completely, helping Jira create release notes effortlessly using real project data.
What This Method Enables for Jira Release Management
This method allows teams to create structured release documentation even if they do not formally create releases in Jira. It supports frequent delivery cycles by grouping updates based on actual activity instead of rigid version tags.
Understanding Custom Variables in Automated Release Notes and Reports
Custom variables allow you to define dynamic fields, such as start and end dates, that feed into your notes. These variables enable your Jira release notes to be flexible and specific to how your team operates, even on a daily, weekly, or ad hoc basis.
Setting Up Date-Based Custom Variables for Release Notes
“Release Start Date” and “Release End Date” are examples of variables that can be configured. These pull all issues that have been updated or resolved within that time frame. It also provides an accurate representation of what has changed without relying on version metadata.
Configuring Your ARNR Template with Custom Variables and JQL
Custom variables can be embedded in ARNR templates and combined with JQL filters. This ensures that when you run the process, the Automated Release Notes and Reports app for Jira will automatically select only the relevant issues that are aligned with your timeframe.
Generating Release Notes Using Date Ranges Instead of Versions
ARNR creates release notes based on the defined date range. This is ideal for continuous deployment or frequent releases, where traditional versioning is not used. You still receive complete, clean documentation.
Previewing & Validating Your Release Notes Output
Before committing, use the preview feature to double-check formatting, grouping, and issue content. This helps to verify that the release notes are professional, accurate, and ready to share with stakeholders.
Why Date-Based Release Notes Are Useful for Continuous Deployment?
Teams that update daily or multiple times per week can avoid the hassle of managing versions. Date-based notes provide clarity and traceability even in hectic settings by allowing you to record real changes.
Full Video Transcript: Generating Release Notes Without Versions in Jira
0:01
[Music]
0:13
Hello everyone, this is Sujit from Team Amoeboids. Welcome to another tutorial. Today we’ll explore the Custom Variables feature in our Automated Release Notes & Reports app for Jira.
0:33
Custom variables help teams who don’t use Jira versions or sprints but release continuously by resolving and launching issues individually.
0:55
Such teams typically prepare release notes by selecting issues resolved within a specific date range weekly, monthly, or custom.
1:15
In Jira, this works using JQL filters with hard-coded dates. But adding these fixed dates into ARNR templates forces manual edits every time, which breaks automation.
1:40
So we introduced custom variables. In ARNR, you can create a Start Date and End Date variable (Date Picker type) and set default values.
2:10
These variables can be referenced anywhere: in the subject line, template body, and most importantly, in your JQL sections.
2:35
ARNR validates your JQL using default values, ensuring it works even before running the template.
2:55
When previewing the template, ARNR asks only for the custom dates instead of version or sprint inputs.
4:10
For example, selecting 1st–30th April fetches all issues resolved in that period. Stories and bugs appear in separate JQL sections.
4:35
Change the range to 1st–15th April, and ARNR instantly recalculates the output.
5:00
If you want the last 30 days, just adjust the variable values. ARNR dynamically retrieves the matching issues without needing new JQL each time.
5:30
This flexibility supports continuous delivery teams who never create Jira versions but still need structured release documentation.
6:00
The same method works for weekly digests, internal stakeholder reports, or customer-specific updates.
6:35
Custom variables also ensure accurate filtering when working across multiple projects.
7:20
You can create variables for other data types too, not just dates, such as text fields or dropdowns.
8:10
For example, a variable can accept a customer name and generate release notes only for that customer.
9:05
This allows deeply personalized reports while keeping templates reusable.
10:00
Every time you run the template, ARNR replaces variables with the selected values and generates the final document automatically.
11:00
No repetitive editing. No risk of forgetting to update hard-coded dates.
12:00
Just clean, accurate, automated release notes.
13:32
That’s all for this video. Thank you for watching!
FAQs
Can I use custom variables with other JQL-based templates in ARNR?
Yes, custom variables integrate seamlessly with any JQL-driven template, giving you complete control over how you create Jira release notes.
Do custom variables work with both Cloud and Data Center versions of Jira?
Jira Cloud and Data Center both support the Automated Release Notes and Reports app, which includes custom-variable functionality.
Is it possible to automate date-based release notes generation on a schedule?
Yes, ARNR allows you to schedule release notes generation using date-based configurations, which simplifies automation for teams with consistent delivery cycles.