https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292013-10-11T13:01:39ZRedmineRedmine - Feature #11907: Custom Field Version (Locked/Open)https://www.redmine.org/issues/11907?journal_id=524452013-10-11T13:01:39ZJulien de BOUILLANNE
<ul></ul><p>+1</p>
<p>We have a custom field "fixed versions" multivalued. All the versions are displayed even if the version is closed (we should display only the locked/open versions)</p> Redmine - Feature #11907: Custom Field Version (Locked/Open)https://www.redmine.org/issues/11907?journal_id=524592013-10-12T09:39:37ZToshi MARUYAMA
<ul><li><strong>Category</strong> set to <i>Custom fields</i></li></ul> Redmine - Feature #11907: Custom Field Version (Locked/Open)https://www.redmine.org/issues/11907?journal_id=537732013-12-12T04:55:02ZDipan Mehta
<ul></ul><p>+1 This is very important. Ideally there should be a check of how the version field should behave.</p>
<p>1. For example, in some cases - only the closed versions should be allowed. e.g. most QA related version tagging - when the bug was discovered, which verison's code had originally introduced this bug, all behave like 'affected_version' type and hence shouldn't allow open version as selections.</p>
<p>2. On the other hand most part of the planning centered custom fields should be in future only hence might allow the open versions but not the closed ones where no more code is yet to be written.</p>
<p>3. Finally, of course there could be no limit to whether version can be past/current/future.</p>
<p>While defining the custom field, there should be a flag that shows how the CF should behave as 'close/open/all' etc.</p> Redmine - Feature #11907: Custom Field Version (Locked/Open)https://www.redmine.org/issues/11907?journal_id=539762013-12-22T14:57:32ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Duplicate</i></li></ul><p>Same as <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Configuration of which versions (by version-status) are shown in version-format custom fields (Closed)" href="https://www.redmine.org/issues/8572">#8572</a>, fixed in 2.5.0.</p> Redmine - Feature #11907: Custom Field Version (Locked/Open)https://www.redmine.org/issues/11907?journal_id=539772013-12-22T14:57:37ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/15735">Defect #15735</a>: OpenID login fails due to CSRF verification</i> added</li></ul> Redmine - Feature #11907: Custom Field Version (Locked/Open)https://www.redmine.org/issues/11907?journal_id=539792013-12-22T14:58:12ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Is duplicate of</strong> deleted (<i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/15735">Defect #15735</a>: OpenID login fails due to CSRF verification</i>)</li></ul> Redmine - Feature #11907: Custom Field Version (Locked/Open)https://www.redmine.org/issues/11907?journal_id=539812013-12-22T14:58:17ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Is duplicate of</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/8572">Feature #8572</a>: Configuration of which versions (by version-status) are shown in version-format custom fields</i> added</li></ul>