Get time spent by field (column) on Jira - jira

I have a board with 3 columns (To-do, Work in Progress and Done).
Is there a way to get the time spent by a card on each column via API?
The getIssue does not fetch this kind of data
Regards

There is no 'time spent by' measure available through the JIRA REST API (as it is too narrow/specific).
There is a possibility to get timestamps of status changes via REST API though. As this answer explains it, you need to use &expand=changelog flag in your API request. In this case response would return created field for each transition that issue has made. You can use it to calculate time between issue transitions.
There is another answer that explains how to get dates using jira-python library (just in case you use it).

Related

Issue with Microsoft Graph Api filter

I am trying to use filter operator to find the events between specific date and time. Now, it only searches single events, any occurrence of recurring events are being excluded.
Following i tried in Graph explorer
https://graph.microsoft.com/v1.0/me/calendar/events?$filter=start/dateTime ge '2022-09-20T00:00:00Z' and end/dateTime le '2022-09-20T23:59:00Z'
it was working all ok few months back and was returning single occurrences of recurring events as well , but now its behaving differently. Can anyone suggest if i am doing something wrong or something changed.
Thanks
Nitin
You need to be using a CalendarView to expand recurring appointments https://learn.microsoft.com/en-us/graph/api/user-list-calendarview?view=graph-rest-1.0&tabs=http . The API shouldn't expand recurring appointment if you make a normal query like your example. This is important if you have any application that is syncing the real exchange store items vs the expanded virtual ones. If it was previously doing that then it was most likely a bug that was fixed.

Calling slack api for data from specific time range

Can you do that? If so, how? I'm using some of the methods here https://api.slack.com/methods but I haven't found any information about using time range as an argument.
When I asked that question I had believed you should ask about date range using extra args field so I had felt like I was specific enough. I believe Slack API docs does not document such use cases as getting date range. Good thing is that there is a tester on the https://api.slack.com/ page.
To get time ranges you need a method that supports that.
Here is an example of such method:
https://api.slack.com/methods/im.history/test

SurveyMonkey API v3 GET Responses fields

In my app I used the get_respondent_list API in API v2 to get an overview of the responses and to allow me to select those responses which were relevant to download in greater detail - fields of interest to me included date_modified, status .
I had hoped that /surveys/{ID}/responses would give a similar facility but all it returns for each response is href and id. The parameters of the call enable me to filter the list in various ways but I would need to make several calls to identify the different categories that I am interested in.
When I made a similar point about the survey list it turned out there was an incorrectly documented include parameter which I could use to get additional fields in the response. I tried that for /surveys/{id}/responses but that was rejected. Could such a facility be added?
If not I guess I will go for /surveys/{id}/responses/bulk and do all the work in the app.
The bulk endpoint is the correct choice. It is basically a call to /surveys/{ID}/responses with 'include' covering every field. The only downside is is the smaller maximum page size. Not sure sure what additional work you are referring to, since you would need to handle pagination at /surveys/{ID}/responses for more than 1000 responses, and all the fields you are looking for are available at the top level of the returned response dictionary.
This wrapper for the API (not written by me) makes it fairly easy to get all the responses from a survey paired with the relevant question details.
In order to get the data structured in a way that resembles the output from the manual export, a bit of gymnastics is needed (I can recommend Pandas' .pivot_table(). Which columns that contain the actual answers vary depending on questions type, adding further complications depending on the complexity of the survey.

Filter data over a period of time in Fabric.io

I have been using Fabric.io on my iOS app for 2 months. It's an e-commerce app so I'm using custom events for monitoring Product search and Purchases. What I noticed it's that though the tables in "Answers" get filled up with data it's not possible to define the date range of the reported query of searching for older events. The dashboard panels look limited to the latest data with no possibilities of customisation.
Is there any way to perform a proper filtering?
Apparently the dashboard only allows you to see the data from the most recent 30 days. If you use the export function you get the data from one year.
They know that some people want to have it, but I don't think they are working on that.
Would be great if everyone could add their +1 on this question:
https://twittercommunity.com/t/fabric-answers-how-to-select-date-range/58599
Hope this helps.

Twitter API 1.1 search/tweets - search by date

Since the "since" param is no longer in use, how can I search tweets older than specific date ? I understand how to use since_id, but in my case I don't have any historic tweet to take the tweet_id from. How is search by date done these days ?
It's an old question, but since it has no answer i share what i have found regarding this question by reading the docs and using the API.
Since and until params are only for maximum 9 past days.
Instead we can use since_id and max_id. You have to set them to unique ids of tweets. You can find one tweet in the specified time (from any user you want). Detect the id by using the API or simply by Developer tools of your browser.
You can use the until param:
Returns tweets generated before the given date. Date should be
formatted as YYYY-MM-DD. Keep in mind that the search index may not go
back as far as the date you specify here.

Resources