I'm trying to get a list of issues assigned to the current logged in user using the JIRA REST API, but I can't find any documentation on how to do that.
What do I need to do in order to get the issues assigned to the current user?
You can specify the issues you want to receive by using jql.
In your case rest/api/2/search?jql=assignee=currentuser() should do the trick.
Here is the relevant part of the documentation of the REST api and here is the description of the used jql-function.
Related
I am new to JIRA API automation and would like to know how I could use the JIRA API to create an issue for specific user who have restricted permissions to view - the API to be used is as follows -https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post
Thanks,
Best Regards,
Nuzhi
I tried going through the API documentation but could not find any particular detailed documentation with regards to the use case.
I have created a Jira search filter, using this request:
POST /rest/api/2/filter
This worked pretty well. Now after I created the filter, I want to get automatically subscribed to it.
Is there a way to do it with the REST API? Or is the only possible way to do this manually?
I already found this in the documentation: https://docs.atlassian.com/software/jira/docs/api/REST/7.4.1/#api/2/filter-createFilter
There, I found the "subscriptions" property, but I can't seem to figure out how exactly I have to write this, to get the correct syntax.
Thanks.
There is a JIRA Feature Request that is still being considered for this to be implemented. Please take a look at this for more details.
For now, all we can do is Fetch or Create Filters using the JIRA ReST APIs but editing the subscriptions should be manual tasks.
Please take a look at the following Atlassian Question which confirms the same.
Details as provided in this Question:
You can do a GET to see the filter subscriptions values you have via:
GET /rest/api/2/filter/favourite?expand=subscriptions
Hope this helps!
Kindly help me to know about - How can we able to get the Campaign and Ad Group created by, created time stamp, modified by, modified time stamp(exactly detailed change history) and whether changes made via automated rules, AdWords API, and AdWords Editor?. through Google AdWords API call.
Unfortunately, it is still not possible to get a change history through the AdWords API.
The last update I found was here on 2016-02-11.
I'd like to be able to add a user as a guest to a project specific to that individual, but it looks like I cannot do this programmatically and must instead resort to manually adding them as a guest. Is there anything I'm missing in the API documentation? Is there an undocumented feature that would let me do so? Or am I just out of luck?
It is currently not possible to manage users of an organization via the API.
This is on our API roadmap, which I hope to publish a public version of soon.
You can subscribe to incremental changes of our API and it's documentation on API changelog https://www.apichangelog.com/api/asana
I'm trying to figure out if there's a way to use the ProfileAdminService (com.ibm.sbt.services.client.connections.profiles.ProfileAdminService) to get one user to follow another user.
I can see that you can do it via a put to /profiles/admin/atom/following.do but I was hoping to just use service.
I've investigated the FollowService but this only (at least that i can see) allows the current authenticated user to follow someone, but I want to be able to get any user to follow someone.
Thanks
The feature was not implemented in the IBM Social Business Toolkit SDK
you can look at the Code for ProfileAdminService and you'll see the methods do not include establishing a following relationship.
You need to use the REST API - http://www-10.lotus.com/ldd/lcwiki.nsf/xpAPIViewer.xsp?lookupName=IBM+Connections+5.0+API+Documentation#action=openDocument&res_title=Following_a_person_using_the_Administration_API_ic50&content=apicontent
with the specified body. You need to craft the URL properly in order to get the feature to work via the REST API