is there an xml url to extract a list of all changes made by a user? I am originally after just the bounds and the changeset id. I have tried the history function in the ID editor but having 4000 change sets it's time consuming and difficult to find the change set I am after.
You can use the OSM API to retrieve changesets of a specific user. It also supports additional parameters like bbox and time.
Related
I want to find out all comments in a User Story/Task made by me in Azure DevOps which contain a certain text.
I know how to make a query that searches for a particular text (the relevant field is "History") but but it will return comments made by anyone.
I can narrow it down to tasks "Assigned To" me, but we usually assign tasks to the PO once they are resolved so the "Assigned To" field becomes useless. Since Azure shows me who made the comment, that info is stored in its db, but is available in its Query Editor?
Edit: A REST API solution would also work for me, if available.
You can query the Get Comments Rest API:
GET https://dev.azure.com/{organization}/{project}/_apis/wit/workItems/{workItemId}/comments?api-version=6.1-preview.3
In the results you will get every comment who created it.
If you want to query many work items in one call you can use Get Comments Batch Api.
Hi you can use query editor to add history for your query clause, comments entered into the discussion area can be queried. These are indexed for full text search.
Items I've been associated with
History Contains Words MyName Or Assigned To Was Ever _ #Me
you can change that based on who you would like to search for using contains word of the username
for more you can learn from Query By history
Assuming I have a field with label FOO in all the envelopes sent, how do I filter the envelopes where the value of FOO is 123456?
I tried setting the search_text parameter with 123456 but it doesn't work.
This is the request I tried to use:
https://demo.docusign.net/restapi/v2.1/accounts/reste_idreste/envelopes?from_date=2021-02-01&search_text=123456
Unfortunately, there's not currently a way to search Tabs/Form Data via the API. We do have long term plans in this area, but nothing firm yet. I would pass this request along to your account team to let them know you are interested in learning more about that functionality as it develops.
The ListStatusChanges call doesn't allow you to pull form data in bulk. You'd need to make one GetEnvelope call per envelope with include=recipients,tabs to pull form data and parse through it yourself.
If this is something you are looking at building out, you could use populate a local database using the GetEnvelope results, and then use DocuSign Connect to automatically pass information about new envelopes moving forward.
It is possible to search for values of Envelope Custom Fields. Moving forward, if your application can populate an ECF, you can then search for that to find specific envelopes.
We have been using Power Bi to access our Rally backlog (Features, User stories). We are planning on including risks and milestones to the extract. We are currently able to successfully retrieve the risks and milestones but not the work items affected by them. Example is Risk RI000 that affects user stories US00000 and US00001.
We want retrieve the 2 work work items affected (US00000, US00001) along with the risk (RI000).
Rally stores WorkAffectedItems as a JSON Web file. From Risks, pull the "WorkItemsAffected.ref" column and you can convert it to a JSON record.
Table.AddColumn(#"PREVIOUS STEP", "WorkItemsAffected", each Json.Document(Web.Contents([WorkItemsAffected._ref])))
You'll then be able to expand the column like you would a normal Record to drilldown to the Formatted ID or whatever you need.
I'm connecting to a third-party web service to retrieve rows from the underlying database. I can optionally pass a parameter like this:
http://server.com/resource?createdAfter=[yyyy-MM-dd hh:ss]
to get only the rows created after a given date.
This means I have to store the current timestamp (using #[function:datestamp:...], no problem) in one message scope and then retrieve it in another.
It also implies the timestamp should be preserved in case of an outage.
Obviously, I could use a subflow containing a file endpoint, saving in a designated file on a path. But, intuitively, based on my (very!) limited experience, it feels hackish.
What's the correct idiom to solve this?
Thanks!
The Object Store Module is designed just for that: to allow you to save bits of information from your flows.
See:
http://mulesoft.github.io/mule-module-objectstore/mule/objectstore-config.html
https://github.com/mulesoft/mule-module-objectstore/
I want to be able to grab data from multiple tags / folders in a users Google Reader.
I know how to do one http://www.google.com/reader/atom/user/-/label/SOMELABEL but how would you do two or three or ten?
Doesn't look like you can get multiple tags/folders in one request. If it's feasible you should iterate over the different tags/folders and aggregate them in your application.
[edit]
Since it looks like you have a large list of tags/folders you need to query, an alternative is to get the full list of entries, then sort out the ones the user wants. It looks like each entry has a category element that will tell you what tag is associated with it. This might be feasible in your case.
(Source: http://code.google.com/p/pyrfeed/wiki/GoogleReaderAPI)
(Source: http://www.google.com/reader/atom/user/-/state/com.google/starred)
I think you cannot get aggregated data as you hope to be able to. If you think about it, even Google lets you browse folders or tags one at a time, and do not aggregate a sub-set of them.
You can choose to have a list of all the items (for each one of their available statuses) or a list of a particular tag/folder.
You could do it in 2 requests. First you need to perform a GET request to http://www.google.com/reader/stream/items/ids. It supports several parameters like
s (required parameter; stream id to fetch; may be defined more than one time),
n (required; number of items to fetch)
r for ranking (optional)
and others (see more under /ids section)
And then you should perform a POST request (this is because there could be a lot of ids, and therefore the request could be cut off) to http://www.google.com/reader/api/0/stream/items/contents. The required parameter is i which holds the feed item identifier (could be defined more than once).
This should return data from several feeds (as returned for me).