This page requires java-script to be enabled. Please adjust your browser-settings.
streber
PM
Login
|
Register
Home
Recent changes
Your Tasks
Efforts
Bookmarks
Overall changes
P
rojects
for
streber commun...
streber
People
Companies
S
earch:
streber
>
Tasks
|
Topics
|
Milestones
|
Versions
|
Files
|
Changes
Help
UI
> Feature (approved)
project should have current version-numbers
/
#81
Move
Bookmark
Summary
For Milestone
v0.069 - security
Status
approved
Opened
Sep 1, 2005
Estimated
30 min ... 2 hours
Completed
100%
Closed
Sep 12, 2006
Created
Sep 1, 2005
/
pixtur
Modified
May 29, 2009
/
ifreeman
View previous 8 versions
Attached files
No files uploaded
Move files
Mark as bookmark
I think about version-numbers as milestones. Like
"this bug was reported in version x.xx".
"this bug/feature/issue was planned be fixed in version x.xx"
"this bug/feature/issue was changed/fixed in version x.xx"
The current project-version should automatically be assigned to new issue-reports.
1 Comments
ifreeman
:
What about...
3 years ago
Projects with concurrent releases? We wouldn't want to automatically choose a version number that's wrong. Setting a default for the current version is fine, even better if integrated with SVN, but it shouldn't be automatic and unchangeable at task creation.
Bug reports? Right now I believe the behavior of the Version field under the Bug Report tab is to use the last used value. It would be a welcome change for that field to automatically assign a current release. That would mean that we would need to be able to set a current release for the project.