https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292008-02-19T08:27:06ZRedmineRedmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=13802008-02-19T08:27:06ZThomas Lecavelier
<ul></ul><p>Hi Sven,</p>
<p>As you said it, it would be a custom field. Custom fields can be created by your redmine administrator. But maybe I hadn't understand your point?</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=13832008-02-19T08:33:48ZSven Schuchmann
<ul></ul><p>Your are right, this would be a custom field.<br />But the custom field should be a drop down list<br />with a all versions of the current project<br />(like "Fixed version").</p>
<p>At this time I am only able to create a custom field of<br />type "list" and enter all versions by Hand.</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=13962008-02-20T09:49:24ZThomas Lecavelier
<ul></ul><p>Ok, so the feature request is more a "add project based data sources for custom field", like Version, affected users and so on... Maybe could we enumerate here all datas that should feed a list in a custom field?</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=14052008-02-21T08:34:35ZSven Schuchmann
<ul></ul><p>In my opinion that would only be two:<br />- Versions in a project<br />- Users assigned to a project</p>
<p>Or am I missing some?</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=25342008-04-30T14:57:58ZSven Schuchmann
<ul></ul><p>Just want to keep this alive...</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=28122008-05-18T18:55:46ZSven Schuchmann
<ul><li><strong>Target version</strong> set to <i>0.8</i></li></ul> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=28262008-05-19T15:40:05ZThomas Lecavelier
<ul><li><strong>Target version</strong> deleted (<del><i>0.8</i></del>)</li></ul><p>Reset "target version" field.<br />It's not the proper way to get a feature implemented...</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=29412008-05-24T05:57:54ZBram Verburg
<ul></ul><p>This one is important for me too, since I know this will be a show-stopper for replacing Bugzilla with Redmine in my organization. I started working on a patch and I could use some input.</p>
<p>I added the following custom field types: users, projects, sub-projects, versions and members. I also added a mechanism to limit types to certain places (e.g. sub-projects, versions and members only work in the context of issues and projects, so they shouldn't be available as a custom field for users).</p>
<p>The problem with projects (and sub-projects) is that projects may be private, and therefore different users will see different lists. Should I drop these two field types, or would be it acceptable to show a list that includes private projects to all users?</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=32632008-06-11T09:46:17ZJames Turnbull
<ul></ul><p>Also interested in this feature - would be very useful.</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=33062008-06-14T05:34:38ZJani Tiainen
<ul></ul><p>+1</p>
<p>Would be very useful feature to be able to populate custom field from standard project data like versions. It's not a big problem to populate lists by hand but still it feels stupid to do that.</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=61662008-12-16T10:10:17ZMichael Aye
<ul></ul><p>+1<br />For me it would be enough to have the possibility of a enumerated custom field. I could fill it myself with data, doesn't have to be project data.</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=73432009-02-15T10:04:52Zgabriel scolan
<ul></ul><p>+1<br />it would be also nice to refer to the repository revision on which the issue has been detected (to trace intermediate version). A solution could be to define a type of custom field as "textilizable" so reference to version, revision or anything else could be done. I won't however provide a "hard" link between the object (as the target version vs issue)</p>
<p>gabriel</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=74142009-02-18T22:30:18ZJerome Vanthournout
<ul></ul><p>+1</p>
<p>Today in this version of Redmine, in the "New Issue" form, there is the field "Affected version" which is a drop list of the different past version.<br />Based on what I understood, this is a custom field with enumerated value. Am I right?</p>
<p>The concern with the custom field is that the new enumerated value can be change only in the administrative form.<br />This is a issue when the project are not managed by the administrators. So, either the custom field with enumerated value can be updated in "project setting" form or the "Affected version" field is linked with the versions of the project.</p>
<p>I would definitely prefer the second option.</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=97262009-06-12T14:10:57ZChristophe Absil
<ul></ul><p>Any news for this feature ? It doesn't seem to be in next release :-(.</p>
<p>What I would like to have is a drop down where you can choose a released version. I like the idea to have a status on version like described in issue <a href="http://www.redmine.org/issues/1245#note-17" class="external">#1245</a>. Depending on this status, the version would be displayed on the drop down or not.</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=137242010-01-20T20:33:21ZSven Schuchmann
<ul></ul><p>This could be the same like <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Custom fields referencing system tables (users and versions) (Closed)" href="https://www.redmine.org/issues/2096">#2096</a></p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=161812010-04-27T11:50:45ZVathanan Kumarathurai
<ul></ul><p>+1</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=183172010-07-14T13:22:17ZGábor Péntek
<ul></ul><p>+1</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=183202010-07-14T14:39:11ZNicholas Kulikov
<ul></ul><p>+1 :)</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=203842010-09-16T13:35:43ZwAy sen
<ul></ul><p>+1 :-)</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=218292010-10-26T21:25:27ZAndré Jonsson
<ul></ul><p>This is quite useful in many situations. +1 :)<br />And having it generalized as "feed custom field with project data (somehow)" sounds like a very nice and flexible idea to go about it.</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=237212011-01-06T00:23:28ZBrian Lindahl
<ul><li><strong>File</strong> <a href="/attachments/5099">affected-version.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/5099/affected-version.patch">affected-version.patch</a> added</li></ul><p>Also added this same comment and patchfile to <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add 'affected version' as a standard field (Closed)" href="https://www.redmine.org/issues/1675">#1675</a>.</p>
<p>Here's a patch you can apply to redmine-1.0.4 to add the 'Affected Version' feature. You can only select 'locked' versions (in my world, these are versions that have made it past integration and internal release). It took me about 3 hours to write, since I don't know my way around the source code and this is my first work in the Ruby language.</p>
<p>/rant<br />For something SO EASY to implement, there's a terrible amount of resistance to implementing this feature. Why? If it's only because people want a multi-selection ability, and that's difficult, who cares! Since it's so EASY to implement, so INCREDIBLY useful, and so DESIRED, implement the single-selection feature now, so that people can start taking advantage of it now! When multi-selection ability is added later to 'Target Version', just add it for 'Affected Version' at the same time.</p>
<p>The resistance to add this feature is just a silly dragging of feet (for 2 years!!!) that I wouldn't expect to see in an open-source project. Heck, I'd be surprised to see this kind of resistance in anywhere but a government contractor waterfall-development world! Are you guys that clueless about the virtues of agile development?<br />/end rant</p>
<p>Now that I'm done ranting, I love your product... except for the lack of this incredibly important feature - it was my biggest resistance to bringing it into my company. Bring my patch into the mainline and finally resolve this issue. Thanks!</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=237222011-01-06T00:36:01ZBrian Lindahl
<ul><li><strong>File</strong> <a href="/attachments/5100">found-version.patch</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/5100/found-version.patch">found-version.patch</a> added</li></ul><p>Actually, on second thought, it should be named 'Found in version'. Since 'Found in version' is quite different from 'Affected versions'. 'Found in version' is the version is was found in, and is filled in by the submitter. It can and should only be a single-selection. 'Affected versions' is filled in by the software engineers when doing version analysis, and can be (and likely is) more than one version. Here is the new patch with the different name.</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=244652011-01-25T18:24:10ZBrian Lindahl
<ul></ul><p>Created a patch issue to follow the progression of the 'found-version.patch' patch file I created. Please relate to <a class="issue tracker-3 status-5 priority-4 priority-default closed" title="Patch: Found-in-version patch (Closed)" href="https://www.redmine.org/issues/7443">#7443</a>.</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=368392012-03-16T10:44:48ZJérôme BATAILLE
<ul></ul><p>+1</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=414212012-10-02T15:59:33ZJudicaël Bedouet
<ul></ul><p>+1</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=414242012-10-02T17:43:53ZSébastien Aubry
<ul></ul><p>+1</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=474752013-03-25T21:01:28ZDipan Mehta
<ul></ul><p>How is this issue any different from <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Custom fields referencing system tables (users and versions) (Closed)" href="https://www.redmine.org/issues/2096">#2096</a>, which is already in the release?</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=545482014-01-29T18:34:04ZJudicaël Bedouet
<ul></ul><p>You are right. I have just created a custom field "Found in version" which fulfils the description of this issue.</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=676302015-12-02T13:45:56ZJakub Rusiecki
<ul></ul><p>Hi all, <br />The custom field is a good start. However (as of RM 2.3.3 at least) full solution should:<br />a) observe Version status - it should be possible to limit list of versions for which it is possible to log error<br />b) allow to soft available versions from most recent</p>
<p>as we have a lot of versions and users/testers often take wrong/old versions.</p>
<p><strong>Any ideas / plugins etc. in this version 2.3.3, please ?</strong></p>
<p>remarks: <br />c) I can not delete versio associated with a ticket; <br />d) sometimes one can crate version per subproject and if we continue in newer project those old versions will not be on the list... <br />e) I know RM 3.0.3 allows to filter it by version status, but this status can not be tailored (we use another field for in Plannning, In Dev, Tests, Shipped, Discarded)</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=713202016-06-06T14:43:27ZDipan Mehta
<ul></ul><p>Essentially, it is not just about the "Found in Version". If there are custom fields based on version - we need qualifiers whether the fields are open, locked or closed.</p>
<p>I guess it would be too much to ask for that they will be restricted by "custom fields" of the version itself.</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=713312016-06-06T16:16:05ZDipan Mehta
<ul></ul><p>Well looks like the demand of this is really there with multiple issues.</p>
<p>But it can be achieved: (As I noted in other issue)</p>
<blockquote>
<p>Basically, you can have a 'custom field' "Type" for each version. And then, when you define any other custom field (for issue or otherwise) which is of type version - it should ask for criteria as "field name" and values can be some conditions. If the field type has multiple values it can be selected which ones applies. The versions qualified under that condition will then be appeared in the corresponding version field.</p>
</blockquote>
<p>Following issues have almost the same demands: Do add related<br /><a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: New Custom Field "Found in Version" (Closed)" href="https://www.redmine.org/issues/685">#685</a><br /><a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: BugTracker enhancement: allow to create a custom field for "occours in version" - end of Life (Closed)" href="https://www.redmine.org/issues/14250">#14250</a><br /><a class="issue tracker-2 status-1 priority-4 priority-default" title="Feature: Show issues with custom field of type Version as related issues in the Roadmap (New)" href="https://www.redmine.org/issues/18560">#18560</a><br /><a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Filterable versions in dropdowns (target version and custom version fields on issues) (Closed)" href="https://www.redmine.org/issues/17962">#17962</a><br /><a class="issue tracker-2 status-1 priority-5 priority-high2" title="Feature: Custom version field that allows filtering versions in the list of options shown by "version's at... (New)" href="https://www.redmine.org/issues/20100">#20100</a></p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=719222016-07-02T03:54:22ZToshi MARUYAMA
<ul><li><strong>Category</strong> changed from <i>Issues</i> to <i>Custom fields</i></li><li><strong>Assignee</strong> deleted (<del><i>Jean-Philippe Lang</i></del>)</li></ul> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=719262016-07-02T03:55:34ZToshi MARUYAMA
<ul><li><strong>Has duplicate</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/14250">Feature #14250</a>: BugTracker enhancement: allow to create a custom field for "occours in version" - end of Life</i> added</li></ul> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=719282016-07-02T04:02:26ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-4 priority-default" href="/issues/18560">Feature #18560</a>: Show issues with custom field of type Version as related issues in the Roadmap</i> added</li></ul> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=1023122021-05-01T14:15:14ZPhilippe Cloutier
<ul></ul><p>Sven, this would be useful, but can you clarify why you ask this to be a <strong>custom</strong> field? I understand that being able to create such a custom field would be an improvement, but would a standard field not address your use case?</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=1023162021-05-03T06:35:43ZSven Schuchmann
<ul></ul><p>Hello Philippe,</p>
<p>I opend this ticket 13 Years ago... I think in the meanwhile you can close<br />it since there a new custom field type "version" which fits my needs :-)</p>
<p>Best Regards,</p>
<pre><code>Sven</code></pre> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=1026072021-05-30T04:50:44ZGo MAEDA
<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>Sven Schuchmann wrote:</p>
<blockquote>
<p>I opend this ticket 13 Years ago... I think in the meanwhile you can close<br />it since there a new custom field type "version" which fits my needs :-)</p>
</blockquote>
<p>Thank you for the feedback and I am glad to see that your original request has been fulfilled with <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Custom fields referencing system tables (users and versions) (Closed)" href="https://www.redmine.org/issues/2096">#2096</a>. I am closing this issue.</p> Redmine - Feature #685: New Custom Field "Found in Version"https://www.redmine.org/issues/685?journal_id=1026082021-05-30T04:50:58ZGo MAEDA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/2096">Feature #2096</a>: Custom fields referencing system tables (users and versions) </i> added</li></ul>