https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292011-01-07T21:49:37ZRedmineRedmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=237902011-01-07T21:49:37ZAlex Last
<ul><li><strong>Assignee</strong> set to <i>Jean-Philippe Lang</i></li></ul><p>Jean-Philippe, I hope you don't mind that I'm assigning this request to you. Maybe you could find some time to implement this in 1.1.0.</p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=264622011-03-15T22:42:10ZRodrigo Recio
<ul></ul><p>I've made a pull request on edavis10's github (my github is rrecio) of a code that expose issue_statuses through REST (I did for trackers too), can anyone do something about this?</p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=271592011-03-26T00:59:21Zmilki milk
<ul></ul><p>I believe I have a better patch than rrecio:</p>
<p><a class="external" href="https://github.com/milki/redmine/compare/master...issue-status-api">https://github.com/milki/redmine/compare/master...issue-status-api</a></p>
<p>I've exposed index/show for issue-status - no longer needs admin access<br />index will list all the statuses<br />show will allow you to retrieve one either by id or name</p>
<p>I've added 3 tests for each one of them.</p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=271602011-03-26T01:30:14Zmilki milk
<ul></ul><p>milki milk wrote:</p>
<blockquote>
<p>I've exposed index/show for issue-status - no longer needs admin access</p>
</blockquote>
<p>I should clarify this. Index is only exposed via api for everyone. Only admin can access the web interface still.<br />Show only exposes an api interface since its not useful otherwise.</p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=279962011-04-15T19:10:00Zmilki milk
<ul></ul><p>I submitted a pull request:</p>
<p><a class="external" href="https://github.com/edavis10/redmine/pull/31">https://github.com/edavis10/redmine/pull/31</a></p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=284252011-04-29T00:40:58ZEwan Makepeace
<ul></ul><p>+1</p>
<p>This is a bit of a showstopper for my friend's iPhone App RedminPro: <a class="external" href="http://itunes.apple.com/us/app/redminepro/id415596033?mt=8">http://itunes.apple.com/us/app/redminepro/id415596033?mt=8</a></p>
<p>I can use it to reject my developers work, but as soon as I find an issue that is completed I am stuck - he is only able to populate the status menu with options seen in the list of issues I pull - and since I only get open issues, he never sees a Closed status, and so it is not on the menu...</p>
<p>Clearly populating menus with the values seen in a small sample of records is no way to be writing a UI but until REST provides enumeration of Status (and other fields) all developers of plugins and desktop software will be similarly stuck.</p>
<p>Related: <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>, <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Include allowed activities list in "project" API response (Closed)" href="https://www.redmine.org/issues/7506">#7506</a>, <a class="issue tracker-1 status-1 priority-4 priority-default" title="Defect: REST API Populating issue field enumerations + Issue list filters (New)" href="https://www.redmine.org/issues/7819">#7819</a></p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=285262011-04-30T21:35:07Zmilki milk
<ul></ul><p>I guess this should be moved to patches instead of feature. Maybe patches are actually seen by developers? Is it stands, the assignee seems too busy or doesn't care about the REST API.</p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=299732011-06-16T05:16:02ZBevan Rudge
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>50</i></li></ul><p>This is related or duplicate of <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> and/or <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>.</p>
<p>It would be great to get this or one of those reviewed and committed.</p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=299772011-06-16T05:19:15ZBevan Rudge
<ul></ul><p>I meant <a class="issue tracker-1 status-1 priority-4 priority-default" title="Defect: REST API Populating issue field enumerations + Issue list filters (New)" href="https://www.redmine.org/issues/7819">#7819</a>, not <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>.</p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=309732011-07-21T21:48:31ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><p>Ewan Makepeace wrote:</p>
<blockquote>
<p>Clearly populating menus with the values seen in a small sample of records is no way to be writing a UI but until REST provides enumeration of Status (and other fields) all developers of plugins and desktop software will be similarly stuck.</p>
</blockquote>
<p>Populating the menu with all existing statuses that <code>/issue_statues</code> would return is (maybe slightly better but) not the right solution. All statuses are not applicable to all issues.</p>
<p>I think the API should offer a way to retrieve the statuses that a particular issue can be changed to by the user. Something like <code>/issues/:id/edit</code> that would return an xml/json representation of possible statuses and all other properties that can be changed (assignee, priority...).</p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=309742011-07-21T21:52:01ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><p>Or maybe a way to include optionnaly all this information in the response to /issues/:id.</p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=309752011-07-21T23:13:25ZAlex Last
<ul></ul><p>in some cases I need to retrieve "*what are the available statuses for this issue*",<br />but sometimes I need to get "*what are all possible statuses in this project*" - that is if I'm building a search form for issues in some application...</p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=318542011-08-29T08:09:12ZEtienne Massip
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li><li><strong>Target version</strong> set to <i>Candidate for next major release</i></li></ul><p>REST-blocking for instances which don't set a default Status.</p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=337192011-11-14T01:42:03ZRodrigo Recio
<ul></ul><p>Why don't you just create a json/xml response for a path like this projects/:project_name/issues/new.json so its response is all current project available trackers and statuses?</p> Redmine - Feature #7180: List of statuses in REST APIhttps://www.redmine.org/issues/7180?journal_id=339222011-11-20T14:29:24ZJean-Philippe Langjp_lang@yahoo.fr
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Target version</strong> changed from <i>Candidate for next major release</i> to <i>1.3.0</i></li><li><strong>Resolution</strong> set to <i>Fixed</i></li></ul><p>The list of all statuses is now available, see <a class="changeset" title="Adds API response to /issue_statuses to get the list of all available statuses (#7180)." href="https://www.redmine.org/projects/redmine/repository/svn/revisions/7878">r7878</a>.</p>
<p>Rodrigo Recio wrote:</p>
<blockquote>
<p>Why don't you just create a json/xml response for a path like this projects/:project_name/issues/new.json so its response is all current project available trackers and statuses?</p>
</blockquote>
<p>Similar to my proposal in note-10. Could you try to design this response so we can get some feedback?</p>