https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292010-06-14T15:10:49ZRedmineRedmine - Feature #5684: new custom field type - "redmine users"https://www.redmine.org/issues/5684?journal_id=173202010-06-14T15:10:49ZFelix Schäfer
<ul></ul><p>I'm not sure I understand what your problem is, but if you want to have a workflow where your developers correct a bug or implement a feature, but that it needs to be verified by an inspector first before it's committed, that's a job for the workflow. You can change the workflow so that developers can only put an issue up to the state "to be verified" from which only an inspector can take it to "closed".</p> Redmine - Feature #5684: new custom field type - "redmine users"https://www.redmine.org/issues/5684?journal_id=173212010-06-14T15:23:00ZMaxim Nikolaevich
<ul></ul><p>Yes, i do this way but... who are inspector?<br />I asked for "inspector" field to allow users with inspector role have acces to task which he should inspect via filter.<br />Yes it's possible to solve this via changing assign role. But this way also not so elegant cause information about how many tasks resolved will be missed in this way.<br />I hope now it's clear.</p> Redmine - Feature #5684: new custom field type - "redmine users"https://www.redmine.org/issues/5684?journal_id=173222010-06-14T15:31:55ZFelix Schäfer
<ul></ul><p>So you're asking for the wrong thing. What need isn't a custom field, I think that would be the wrong approach, what you want is way to filter issues with regard to a certain transition, so something like "show me all issues set to status "to be verified" by Maxim", right?</p> Redmine - Feature #5684: new custom field type - "redmine users"https://www.redmine.org/issues/5684?journal_id=173232010-06-14T15:41:04ZMaxim Nikolaevich
<ul></ul><p>Yes, you are right. Are there other way to do this except custom field?</p> Redmine - Feature #5684: new custom field type - "redmine users"https://www.redmine.org/issues/5684?journal_id=223172010-11-12T10:04:40ZNils Linde
<ul></ul><p>I totally agree. There should be a custom field type "User" and "Group", so it could be used to add fields to issues.<br />Usage examples:<br />"Feature user" if problem is for antoher user, but new issue is added by another user<br />"Group manager" if groups are used to define departments in company (not speaking about possibility to set a parent/child group id/name, to make group hierarchy), it is good, to be able to define different roles for groups<br />"Assigned group" to assign a specific group to issue, for example, Technical department. If group is added to issue, the group manager is noticed (if "Group manager" function is avilable)</p>
<p>I can think tons of more usages for this stuff and that should not be hard to implement, as there already is field "Assigned user", that is for issues.</p> Redmine - Feature #5684: new custom field type - "redmine users"https://www.redmine.org/issues/5684?journal_id=229132010-12-02T04:50:21ZMaxim Nikolaevich
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>This issue dup <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 #5684: new custom field type - "redmine users"https://www.redmine.org/issues/5684?journal_id=252372011-02-16T11:11:53ZEtienne Massip
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li><li><strong>Resolution</strong> set to <i>Duplicate</i></li></ul><p>Closed as duplicate of <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>