Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Is is possible to have the release notes use another version field?

The current behavior in JIRA is to create the release notes based on the fix version.

In our JIRA data model we have defined another version picker field called Target version (used to identify the branch on which the issue will be fixed).

Is there a way to have the release notes use this field instead of the native fix version?

Best would be to be able to produce the release note either on fix or target version.



2 answers

PDF View Plugin for JIRA can generate a Release Notes document from any JQL query.

That means you can use a "version = 1.2.3" (built-in field) or "MyCustomVersionField = 1.2.3" (custom version picker) JQL condition to get the two lists of issues, and transform those to PDF to implement your two use cases.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you