[#JRA-4080] Create a property of version called 'Release Type'

JIRA

Create a property of version called 'Release Type'

Created: 21/Jul/04 05:36 PM Updated: 28/Jul/04 02:12 PM

Component/s:

Administration

Affects Version/s:

2.6.1 Enterprise

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Part

This issue incorporates:

~~JRA-1582~~ Scheduled release date for unreleased versions

Participants:	Greg Perrott and Owen Fellows
Since last comment:	208 weeks, 1 day ago
Labels:

Description

« Hide

It would be nice to be able to specify a release type (e.g. Alpha, Beta, Production etc).

This change will also enable us to be able to distinguish between defects reported during UAT as apossed to defects in a proudction release.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

denis@atlassian.com - 21/Jul/04 09:52 PM

Have you looked at the linked issue? It incorporates many of the issues that you mention (apart from release type).

Is release type important to you? What do you require?

[ Permlink | « Hide ]

Greg Perrott - 22/Jul/04 03:47 PM

Denis,

I don't understand how using Linked Issues would acheive what is stated above.

What we want be to able to do is:
1. Report on the release schedule for a given system. This means the planned furure releases, when they will be scheduled, what type os release and what changes make up that release. We have developed a number opf reports already using Crystal Reports and we would do the same here if the data was available in the JIRA database.

2. We would also like to be able to measure defect discovered in Test Releases vs. Defects discovered in Production releases. At the moment we use only one version regardless of the number of actuall releases.

[ Permlink | « Hide ]

denis@atlassian.com - 22/Jul/04 07:51 PM

Sorry for the confusion. I meant that you should have a look at the issue that is linked to this issue (~~JRA-1582~~). It probably solves your problem.

Can you let us know if that is the case?

[ Permlink | « Hide ]

Greg Perrott - 22/Jul/04 08:54 PM

Sorry for the confusion.

The linked issue addresses the release date but not the release type.

Can this issue should be updated to reflect the request for a version release type and ignore the release date?

Greg.

[ Permlink | « Hide ]

denis@atlassian.com - 25/Jul/04 11:40 PM

Updated issue to change the issue type & summary to reflect new issue.

[ Permlink | « Hide ]

Owen Fellows - 28/Jul/04 02:12 PM

To work around this you could create three version for each Version e.g. 1.0 alpha, 1.0 beta, 1.0 final

You would not release the alpha until you where very happy with but you could still raise Issues against it.
These Issues would have a fix for version of 1.0 alpha and 1.0 final (To allow you to track progess of the entire version).

This way you can see all Issues that need to be fixed for each release of the version as well as keeping track on when the Issue was raised.

Does this give you the required functionality?