Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to document releases and share release notes

Deleted user Mar 08, 2021

Anyone doing this process to create Release notes both internal and for Customers (external ) ?

Not clear how to use as we have multiple releases (builds or modules) within a product.

One product with multiple releases within that product.             Example: product 2021 comprised of product 2021-A,  product 2021-B,  product 2021-c-f, 

1 answer

Hi Todd, 
I am currently exploring this and keen to hear your experience on generating Release notes.
At my organisation we have many Products, used by many customers. Not all customers are on the same version of the Product too, i.e we have many versions of the Product/s out there.
When we make changes(new features, bug fixes) we would like to generate and share Release notes to external customers(via our internal staff who are customer liaison).

Basically, for every change there is affected Version/s of software & we have a new fixVersion for the changes.
For every release I'd like to build Release notes which lists out :
- Changes in the Release, and  
- Customers affected

So that, only the affected Customers are sent the release comms. We would love to do this via JIRA ITSM(aka JIRA service desk) where possible

Reaching out to the community, to see if anyone has solved this kinds of problem

@Ravi Tata Did you find an approach that works for you?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events