FYI, an OSLC implementation for JIRA has been made available as described here: https://jazz.net/library/article/766

Perhaps a misplaced question but does this being done mean that IDE connectors (like Eclipse Mylyn) now can get custom fields during issue creation/modification? I'm asking for I have experienced this and wanted to know if Jira update can solve this. Also have seen JRA-11597 and noticed that it was fixed within Jira 4.4. Since I'm not really familiar with nor Jira nor IDE connectors API, am not sure if both issues being closed actually makes it possible for Mylyn to work and create issues or not.

Matt,

There is no single issue for future REST work. There is a new component in JIRA that REST issues use.

Or perhaps link the new issue for tracking this in 4.3 back here.

How can you mark an issue as resolved when it isn't actually resolved? Why don't you link the smaller tasks to this one so the people who are watching this issue can be informed of progress.

JIRA 4.2 introduces an alpha version of this and further work will be done in 4.3 and future releases to expand upon that alpha. The API docs can be seen here.

While we clearly have a lot of work to do before we've got something that can replace SOAP, much less address the shortcomings in the current remote API, this will be better tracked in smaller-grained issues rather than a big overarching one like this.

Subtask creation through REST would be hugely beneficial

It would be nice to have the ability to update a single field of an existing issue. Please include the ability to update custom fields, including cascading select fields (which always seem to be left out of important functionality for some reason).

We have several python scripts that we use to do this kind of thing right now and it's pretty difficult. The Jira screens can be driven from the script, but the edit screen for our issues contain way too many fields to handle easily (and the script would have to be updated whenever new fields are added). So we end up creating hidden transitions in the workflow that have transition screens with just the fields we're interested in. It works, but it would be far, far, easier if we could just use a REST api to provide the issue id along with the field(s) and corresponding value(s) to be updated.

There are two things we need which aren't in the SOAP API: link issues to each other; and read/write Watchers.

You should consider making the JIRA REST API conformant with the Open Services for Lifecycle Collaboration (OSLC) interface for Change Management (OSLC-CM). This would allow JIRA to integrate with ALM tools from IBM, Oracle, Rally, SourceGear, etc. The Mylyn folks are already involved. Here's the link to the OSLC-CM home page: http://open-services.net/bin/view/Main/CmHome. OSLC-CM v1 is the current spec and work on v2 is underway. It's an open effort and we'd love JIRA and/or JIRA users to join in and help us define v2.