Feature #3000: New issue - Affected version droplist - Redmine

Actions

Copy link

Feature #3000

closed

New issue - Affected version droplist

Added by Steve Diver almost 16 years ago. Updated about 15 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

2009-03-18

Due date:

% Done:

Estimated time:

Resolution:

Duplicate

Description

We would very much like to see the option to specify the affected version of our projects, when issues are reported.

Based on the Target version droplist, tagging of the version that the bug affects, would greatly aid the debugging process.

Related issues

Actions

Copy link

Updated by Steve Diver almost 16 years ago

Status changed from New to Resolved

Somehow I had missed the previous talk on this, but the feature does not show as having been applied, even though it clearly is there on the redmine.org new issue page.

Actions

Copy link

Updated by Holger Winkelmann about 15 years ago

Steve Diver wrote:

Somehow I had missed the previous talk on this, but the feature does not show as having been applied, even though it clearly is there on the redmine.org new issue page.

did you found how to use this feature with a current redmine version ? I cant find anything about affected version. Even I can see it on the www.redmine.org system.

Actions

Copy link

Updated by Holger Winkelmann about 15 years ago

why this issue is resolved if it is a dup of #3824 and seems not to be implemented ? should we reopen this ?

Actions

Copy link

Updated by Jean-Philippe Lang about 15 years ago

Status changed from Resolved to New

Steve Diver wrote:

Somehow I had missed the previous talk on this, but the feature does not show as having been applied, even though it clearly is there on the redmine.org new issue page.

Here on redmine.org, "Affected version" is a custom field.

Actions

Copy link

Updated by Dan MacMillan about 15 years ago

This is a rather important feature. However I don't think it should be implemented by a dropdown, rather it should be a multi-select, because issues can affect multiple versions of software and it's key to track which ones.

Alternatively, although I think it's far from ideal, it could be implemented as a custom field ... if custom fields were changed so that a multi-select kind of list was implemented.

Actions

Copy link