-
Suggestion
-
Resolution: Answered
-
None
Hello,
I'm new here, but I have worked with Jira for some time now, so have at least a basic idea about how it works etc.
We aren't done with our software yet, so the "release comments"-matter wasn't that important yet, but soon we will be ready and so I'm looking into the templates for release comments at the moment.
Because of this I was able to deal with that matter recently and I have to agree with many users, which posted here: Jira's release notes templates are somewhat out of date and compared to the really great piece of software (Jira itself), their inelasticity and inflexibility are very untypical.
Ok, there are quides how to customize the templates, but that's not an easy task, especially not for people like me, who don't have an idea about java programming etc.
Issue navigator -> saved filters doesn't meat all the requirements users might have or do have.
I also would like to see some changes here in the feature.
For our case I was thinking about something like this:
- defining of the title for the release notes: "Release notes for the version <current_version>"
- defining of the group type: at the moment it's "issueType.name" (Bug, New Feature, ...). We would rahter like to use "resolution.name" (Fixed, Added, ...), since that is the part, which is important to the customer, not the title of the issue, which was entered while creating. Many different issueType.names can lead to a single resolution.name (Bug, To Clarify, Question -> Fixed etc.)
- defining of issue-Types and resolution-types, which shall be considered by the creation of release notes instead of taking all of the issues for the current version or to edit the templates all the time
- defining / formatting of the fields, which shall be used and visible for each entry (issue.key, resolution.note (should be available by default and be a "must fill in"-field instead of creating a selfdefined field), issue.summary, resolution.date, ...)
- storing of different templates and the ability to choose one them before generation (one should be defined as default). For example: that way it would be possible to easily generate public release notes for customers and then private release notes with inetrnal entries and comments etc.
So basically some some text and structure templates with some variables / place holders and storage / selection of several templates defined that way.
More or less the same, what users are asking about on the forums many times.
That would make Jira much more enjoyable than it is already.
Regards,
Mark
- is duplicated by
-
JRASERVER-22373 Ability to generate Release Notes against a filter
- Closed
- relates to
-
JRASERVER-3526 Include component in the release notes
- Closed
-
JRASERVER-3536 Release Notes should say "won't fix"
- Closed
-
JRASERVER-5447 Release notes included issues that have not been fixed.
- Closed