Page 1 of 1
change versions
Posted: 05 Nov 2007, 12:36
by hung
I have a project released already, and now customers request some new features. Meanwhile there is a field named Severity, which has "feature" value, in Product version, users cannot choose new version - which is added to project, but not release yet.
I have to change version status to released for users choose new version. But I dont think it's a good idea, cause it's still developing.
How to change versions in my case?
Re: change versions
Posted: 05 Nov 2007, 16:53
by Tinjaw
I don't do things that way. If customers are requesting a feature I have them use the version of the product they are currently using. It is not up to the customer to determine if I am going to 1) acknowledge their request as valid 2) do anything about it 3) decide to put it in the next version. If the feature request is valid, I will acknowledge it. At some point I may decide to implement it and then I chooses a target version for the ETA.
Hope that helps.
Re: change versions
Posted: 06 Nov 2007, 04:38
by hung
Yes, got your points. However, even after reviewing the requests, I decide they're good features and want to put into new version, but click to "update issue", I, the developer or even the administrator, cannot choose new version if its status is not released
Re: change versions
Posted: 06 Nov 2007, 07:34
by deboutv
Like Tinjaw said, you have a Target Version field to specify in which version the feature will be implemented.
Re: change versions
Posted: 06 Nov 2007, 10:39
by hung
ok, got it. I needed to switch to Update Advanced to get the Target version field
Why not choose View Advanced / Update Advanced as default?
Re: change versions
Posted: 15 Nov 2007, 16:25
by vboctor
You can do that by setting the following configuration options in config_inc.php:
Code: Select all
# --- advanced views --------------
# BOTH, SIMPLE_ONLY, ADVANCED_ONLY
$g_show_report = ADVANCED_ONLY;
$g_show_update = ADVANCED_ONLY;
$g_show_view = ADVANCED_ONLY;