https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292011-03-28T22:34:42ZRedmineRedmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=272402011-03-28T22:34:42ZRodrigo Recio
<ul><li><strong>File</strong> <a href="/attachments/5702">restadditions.diff</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/5702/restadditions.diff">restadditions.diff</a> added</li></ul><p>This patch contains additions that lists issue statuses and trackers.<br />It does exposes assignable users and versions inside the issue.</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=299702011-06-16T05:08:01ZBevan Rudge
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>50</i></li></ul><p>It would be great to get this reviewed and committed.</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=299752011-06-16T05:18:29ZBevan Rudge
<ul></ul><p>This is related or duplicate of <a class="issue tracker-2 status-5 priority-5 priority-high2 closed" title="Feature: List of statuses in REST API (Closed)" href="https://www.redmine.org/issues/7180">#7180</a> and/or <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: REST API new features (Closed)" href="https://www.redmine.org/issues/4968">#4968</a>.</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=309862011-07-22T10:07:55ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><p>Bevan Rudge wrote:</p>
<blockquote>
<p>It would be great to get this reviewed and committed.</p>
</blockquote>
Quick review:
<ul>
<li>your patch makes the tracker and status lists accessible to administrators only</li>
<li>no tests</li>
</ul> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=309892011-07-22T10:47:55ZEtienne Massip
<ul></ul><p>Jean-Philippe Lang wrote:</p>
<blockquote>
<ul>
<li>your patch makes the tracker and status lists accessible to administrators only</li>
</ul>
</blockquote>
<p>Actually, lists are already accessible to administrators only (in admin screens) ?</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=309912011-07-22T11:05:02ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><p>Indeed. But if the goal is to let users retrieve trackers and statuses in order to fill an issue form or set filters, it doesn't work.</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=309922011-07-22T11:59:26ZEtienne Massip
<ul></ul><p>Sure. But it would be illogical to give read-only access to these lists by API and not by application screens, wouldn't it be?</p>
<p>I mean, to keep some consistency, this might be the concern of a second patch which would add a new <cite>read access to referential data</cite> permission which would also allow direct access to application screens via URLs like <code>/issue_statuses</code>?</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=309932011-07-22T12:55:47ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><p>Etienne Massip wrote:</p>
<blockquote>
<p>Sure. But it would be illogical to give read-only access to these lists by API and not by application screens, wouldn't it be?</p>
</blockquote>
<p>Not so illogical if you consider that, unlike API users, web users <em>do not need</em> to access a simple read-only view of trackers or statuses.</p>
<blockquote>
<p>I mean, to keep some consistency, this might be the concern of a second patch which would add a new <cite>read access to referential data</cite> permission which would also allow direct access to application screens via URLs like <code>/issue_statuses</code>?</p>
</blockquote>
<p>Users with a <code>view_issues</code> permission already have access to ids/names of all trackers and statuses at /issues (look at the filters). Having a permission to give access to a different <em>representation</em> of the same information is far from ideal.</p>
<p>I think that /trackers and /statuses should be open to API calls by non-admin. But what would be the point to have an html view other than for admins?</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=310112011-07-23T12:38:06ZEtienne Massip
<ul></ul><p>Jean-Philippe Lang wrote:</p>
<blockquote>
<p>Users with a <code>view_issues</code> permission already have access to ids/names of all trackers and statuses at /issues (look at the filters). Having a permission to give access to a different <em>representation</em> of the same information is far from ideal.</p>
</blockquote>
<p>Except that they can view issues of visible projects only, that's not exactly the same representation.</p>
<blockquote>
<p>I think that /trackers and /statuses should be open to API calls by non-admin. But what would be the point to have an html view other than for admins?</p>
</blockquote>
<p>I guess no point, you're right. I was just wondering if it was logical to get a <code>403</code> with <code>/issues_statuses</code> and the full issue statuses list with <code>/issues_statuses.xml</code>. That somewhat means handling rights depending upon required format.</p>
<p>Anyway, I'm discussing something that is not very useful, I agree with that.</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=310142011-07-23T13:32:00ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><p>Etienne Massip wrote:</p>
<blockquote>
<p>Except that they can view issues of visible projects only, that's not exactly the same representation.</p>
</blockquote>
<p>Not matter which issues or projects they can see, they can always see the list of <strong>all</strong> statuses and trackers in the filters.</p>
<blockquote>
<p>I guess no point, you're right. I was just wondering if it was logical to get a <code>403</code> with <code>/issues_statuses</code> and the full issue statuses list with <code>/issues_statuses.xml</code>. That somewhat means handling rights depending upon required format.</p>
</blockquote>
<p>Maybe a 406 would be more appropriate :-)</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=310162011-07-23T13:58:56ZEtienne Massip
<ul></ul><p>Jean-Philippe Lang wrote:</p>
<blockquote>
<p>Not matter which issues or projects they can see, they can always see the list of <strong>all</strong> statuses and trackers in the filters.</p>
</blockquote>
<p>Oh, sorry, I thought they could only see statuses used in workflows tied to trackers of the project.</p>
<blockquote><blockquote>
<p>I guess no point, you're right. I was just wondering if it was logical to get a <code>403</code> with <code>/issues_statuses</code> and the full issue statuses list with <code>/issues_statuses.xml</code>. That somewhat means handling rights depending upon required format.</p>
</blockquote>
<p>Maybe a 406 would be more appropriate :-)</p>
</blockquote>
<p>405 ? :o</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=310242011-07-23T14:28:23ZEtienne Massip
<ul></ul><p>Not 405, 406 is right.</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=318592011-08-29T08:13:33ZEtienne Massip
<ul><li><strong>Target version</strong> set to <i>Candidate for next major release</i></li></ul><p>Pushed for complement of <a class="issue tracker-2 status-5 priority-5 priority-high2 closed" title="Feature: List of statuses in REST API (Closed)" href="https://www.redmine.org/issues/7180">#7180</a> and <a class="issue tracker-2 status-1 priority-5 priority-high2" title="Feature: REST API - Enumerations (New)" href="https://www.redmine.org/issues/7402">#7402</a> for custom fields.</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=337422011-11-14T17:50:51ZAlex Last
<ul></ul><p>I think this should be moved to version 1.3.0</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=514692013-08-30T08:37:29ZJaap de Haan
<ul></ul><p>Relates to the newer ticket <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: REST API for getting CustomField definitions (Closed)" href="https://www.redmine.org/issues/11159">#11159</a>, asking for the implementation of export of custom fields information.</p> Redmine - Defect #7819: REST API Populating issue field enumerations + Issue list filters https://www.redmine.org/issues/7819?journal_id=516472013-09-08T23:45:22ZToshi MARUYAMA
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-5 priority-4 priority-default closed" href="/issues/11159">Feature #11159</a>: REST API for getting CustomField definitions</i> added</li></ul>