[#JRA-9561] Allow source control (e.g. CVS) information to be included in release notes

JIRA

Allow source control (e.g. CVS) information to be included in release notes

Created: 05/Mar/06 09:44 PM Updated: 12/Mar/07 01:34 PM

Component/s:

Reports

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

JRA-7835 Option to remove sub-tasks from roadmap / changelog / Release Notes

JRA-3526 Include component in the release notes

This issue is related to:

JRA-3526 Include component in the release notes

Participants:	Anton Mazkovoi [Atlassian], Antonio Vollono and Benjamin Naftzger [Atlassian]
Since last comment:	1 year, 24 weeks, 3 days ago
Labels:

Description

« Hide

A customer has requested the ability to be able to easiliy add source control information (CVS, Subversion, Perforce) to JIRA's release notes.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 06/Mar/06 04:09 PM

Release notes generally is a very 'custom' thing, as different customers want totally different things in teh release notes. We can bundle a few more sample release note tenplates that show what sort of thinsg can be done with custom release notes.

[ Permlink | « Hide ]

Antonio Vollono added a comment - 28/Jul/06 05:14 AM

On this issue I have added a post in the Atlassian forum on "JIRA Dev" that I report hereafter, after having received a feedback from Nick.

--------------------
taken from : http://forums.atlassian.com/message.jspa?messageID=257231027#257231027
Releases wrt CVS tags
Posted: Jul 21, 2006 12:05 PM

Hi,

I am going to (and I will ...!!..no doubts) procure JIRA for my company. I am promoting it internally with the trial version. While "playing" with the tool to understand how it works we got a couple of questions and requests (for improvements if not available). I'll post here one (I hope it is the right place).
We do like the concept of "Release" and in the tool already it covers the need to know "which issues" have been "closed" in each release. Now, since the tool already "talks" with CVS, would it be possible to set for each Release a "CVS tag" such that, on demand, the tool connects to CVS server and gets back all the modules, with version, having this tag? In this way, for JIRA one could have informations on which "issues" have been covered and which are the SW modules with version used in the "release".
A Report containing both information would be great.
Is this feature (feature and report) a possible "improvement" in JIRA system roadmap?

These kind of information (version of each module part of a release)
normally goes into a Revision and Release Note document that in IT medium/large Project became a standard to be delivered for each major Release of a System.

Thanks
Antonio
-------------------

[ Permlink | « Hide ]

Antonio Vollono added a comment - 12/Mar/07 01:32 PM

Being able to "add" informations to a Release Note, such as :

1. list of RPMs
2. list of CVS modules compiled (you can simply allow to specify a "cvs tag" to be searched in all modules declared for such Project". The lost of modules found can be used as "CVS notes")
3. documents accompanying the Release (attach files is the simplest way. More complex would foreseen a small conf mgmt of docs....but this is probably too much)
4. list of Sites/Users having installed the specific release
5. URL in which the Release can be downloaded.

would really make of JIRA the "outstanding", "superb", "gorgeous", "most popular" tool for "issue management".... I'm looking for votes here. I know that there are lot of other "JIRA users" willing to have this. Come on! vote it!