JQL get hours logged per person per day - jira

Hi guys so I am trying to make my life a bit easier and figure out how to get the values logged against different tasks by the same person in 1 day so I can basically get the sum of their hours logged in total. Currently I can do this via the browser filter option using:
worklogAuthor = currentUser() AND worklogDate = "2019/01/30"
The problem is it returns entire tasks not just the hours so I need to click through each task and then get the number against the work log. Is there a way I could limit the fields being returned so I just see the work logged and maybe the task id? I see that there is some documentation out there to do that but I haven't been able to get it quite right yet.

Given that it has been 2+ years, I hope you have since found another approach. The issue you are bumping into is simply that the Advanced Search will only return a list of tasks, you can't modify that "select". What I would recommend is leveraging either the reporting or dashboarding functionality. The 2 widgets that I would recommend would be either Issue Statistics, or Workload Pie Chart. Worst case scenario, you can always dump the data out to a csv or retrieve from an API and aggregate your data that way as well.

Related

Get new emails with microsoft graph

I am trying to get only new emails with microsoft graph.
Iam doing this by checking date like
GET https://graph.microsoft.com/v1.0/me/messages?$filter=receivedDateTime+gt+2016-06-06T08:08:08Z
Is there any possibility to build query to get new messages but base on id instead of receivedDateTime? Something like: get messeges until you find id=....?
I think the delta query solution is pretty good (as suggested in a different answer). However, for my purposes, there were two major drawbacks: 1) it's in preview (beta) right now, so it makes it less than ideal for production code and 2) it doesn't seem to support the monitoring of all messages, just those in a particular folder.
I actually prefer the solution you're working with. The timestamp in the header of the response can be used to reset the time field in you query, so that if you have "receivedDateTime gt 12:00:00" and get back the server time of 12:01:00 for your request, you can use "receivedDateTime gt 12:01:00" next time.
The scenario you're looking for is specifically what the new Delta query is designed to support. Deltas allow you to retrieve changes to a given folder (i.e. Inbox) since you last polled that folder. Message IDs not static or consecutive so they're not a suitable property for determining new vs. old messages.

How can be created a filter in jira that contains the sum of time spent and time budget of the issues of all epics?

I´m trying to create a gadget for the Jira Dashboard that´s quite hard to accomplish.
I need to show a list of epics with time budget and the sum of time spent as columns.
The problem I´m facing is that the time logged is not made in the epics, but in the tasks or issues inside the epic (as I think it should be) and the column on "sum of time spent" is always empty.
This means, as I see it, that I have to be able to sum up the issues inside every epic and somehow show it in the empty column of the epic I need to see.
I created a filter and I´m calling it with the "filter results" jira dashboard gadget.
I tried with the Script Runner plugin and read the API it has, but still no idea how can that be done.
Is there any idea?
Thanks in advance for any advice.
I have looked for something exactly like this recently, and am surprised that JIRA doesn't have a way to do this out of the box.
Checkout Epic Sum Up. https://marketplace.atlassian.com/plugins/aptis.plugins.epicSumUp/cloud/overview It will solve the Time Budget question, but I don't know about a Time Logged solution.
See:
https://confluence.aptis.info/display/ESU/Time+Field
"How to search a Time Field by using JQL"
You might also find some useful features in the Tempo Addon.
https://tempoplugin.jira.com/wiki/display/TEMPO/Tempo%20Timesheets%20Documentation
Since you're looking to display something on a dashboard look under the Users Guide: Tempo gadgets area.
this works with the Plugin Timesheet
https://marketplace.atlassian.com/apps/294/timesheet-reports-and-gadgets?hosting=cloud&tab=overview
1) Add the Gadget to a JIRA-Dashboard
2) Edit the Gadget appropiately
but care that you
Group by: Epic Name
and choose for
Additional Fields: Original Estimate and Remaining Estimate
Consider to set Show Details: to No
This will look something like this:
(Remaining Estimate are the numbers Right from the Original Estimate-column )

Are Asana stories guaranteed to be returned in time order sequence?

While trying the Asana API for task stories I noticed that the server sends back a list of all the stories in time-ordered sequence i.e sorted on the created_at field. The first element in the list is the first story of that task and the last item is the latest story. Is this ordering guaranteed by design? And can this be relied upon in the code? I want to get the latest activity by looking at the last element of the returned list. Documentation has no such information.
You're correct, we order stories by creation time in any situation where you get a set of stories. I'm adding that to the documentation now. Thanks for the catch!

Accessing huge volumes of data from Facebook

So I am working on a Rails application, and the person I am designing it for has what seem like extremely hefty data volume requirements. They want to gather ALL posts by a user that logs into the application, and all of the posts for each of their friends for the past year.
Before this particular level of detail was communicated to me, I built the thing using the fb_graph gem and would paginate through posts. I am running into the fact that first it takes a very long time to do this, even when I change the number of posts requested per page. Second, I frequently run into the Oauth error #613, more than 600 requests per 600 seconds. After increasing each request to 200 posts I run into this limit less, but it still takes an incredibly long time to get all of this data.
I am not particularly familiar with the FQL alternative, but it seems to me that we are going to have to either prioritize speed or volume of data. Is there a way that I am missing that would allow me to quickly retrieve this level of information?
Edit: I do save all posts to the database as I retrieve them. What is required is to make one pass through and grab all of the posts for the past year, for the user and friends. This process takes a long time and I am basically wondering if there is any way that it can be sped up.
One thing that I'd like to point out here:
You should implement some kind of local caching for user's posts. I mean, instead of querying FB each time for the posts, you should save the posts in your local database and only check for new posts (whenever needed).
This is faster and saves you many API requests.

Amazon Product API - How to get items for sale by price?

I have a strage requirement from a client, he needs to display a ramdom selection (100 - 200 items from mixed categories) of products for sale on & shipped by Amazon but ordered by price. The idea is to allow people find gift ideas based a user input price point.
I have been looking through the API docs but cannot see an obvious way to find search by price, I am thinking of writing a script to "copy" large parts of the amazon product catalogue into a local database & have it update every few weeks, then use this for user searches, but this does not feel right / their must be a better way.
Has anyone any experience with this type of problem? Thanks!
You would want to use the Amazon Product Advertising API. Using this API you would want to perform a SearchIndex-ItemSearch query. Possible parameters to ItemSearch are available on the API Docs here
You can see in the docs that you cannot query by MinimumPrice and MaximumPrice on SearchIndex: All. However, if you search specific indexes, it allows you to do a price related search.
I would guess that you can agree with your client which categories should the items be from. Then you can just query them one by one.
Amazon's database changes very often. Hence, caching data for a week without updating may not be desirable.

Resources