Is there anyway to find the last 10 JIRAs I have worked on - irrespective of time period? By worked on, I mean any thing I have updated. Thanks.
You could query the activity stream.
For example here are my last (up to) 10 issues on jira.atlassian.com in ATOM format:
https://jira.atlassian.com/activity?provider=jira&maxResults=10&streams=user+IS+david#davidsimpson.me
If you want authenticated, try appending parameters &os_username=a.n.other&os_password=abc123 (or similar) to the URL.
Incidentally, an activity stream similar to this is present in your JIRA profile, e.g. https://jira.atlassian.com/secure/ViewProfile.jspa?name=david%40davidsimpson.me
Related
is there a way to query for next 5 instances of given series? I am querying using time-frame:
1. ask for all the meetings for next 7 days for all user events
2. Go over each event fetched and check if event has masterSerieId
3. Return matching instances.
This feels (and is) a bit painful.
Can i request next X instances of master series right away? I can't just simply or 'simply' get them based on recurrence rule, as some might have expired.
I could image I could ask for a year ahead and pass as a query parameter masterSeriesId and limit output with $top. Is that right approach?
Based on this document, you could call /events//instances – given a start time, returns all instances in the requested time frame of the meeting specified by the provided series master ID
I want to get all video comments of a channel. At the moment I'm proceeding like this:
1.) Getting all video ids of a channel (1 quota)
2.) Sending new request with "part: statistics" and getting the total comment count to a youtube video (2 Quota)
It's polling in 30 seconds intervall and I wanted to reduce the quota. Therefore is there a possibility to query whether there are any new comments for a channel videos (Total amount of comments for a channel including channel comments would be fine too)? Like saving the old value of total amount of comments and comparing it with the new amount of the query?
No, from my experience.
I would not use video's commentCount.
- you can pull over 260 comments from a video whose comment count is only 243. https://www.youtube.com/watch?v=87xYGDR_eME
I would not try optimizing by stopping at recent comments.
- this would work for threads, but each thread has replies. So you have to check each thread anyways just to see if they have new replies.
- note: it's dangerous to use commentThreads' reply mode, as it may only return a subset of replies. Instead get a comment list using parentId.
Perhaps, if you sort by time and save the id of comments you've collected, you can use cheap requests like id to figure out which comments are new and pull them with snippet.
- stop when you get to an id you've already gathered.
This may not be simple though because publishedAt or updatedAt leave two questions:
will an old comment be bumped to the top if it's edited? If so, you can't stop once you recognize a comment id, because it might have jumped ahead of new comments (unless the change the id when it's edited).
will the old comment not be bumped if edited? If this is the case, you need to check snippet for each comment as the textDisplay may be different. In this case I can see no optimizations.
I just added a release that wasn't on musicbrainz before:
http://musicbrainz.org/release-group/8f6f6155-20dd-4960-9381-47805e6b50f5
Here's my query for that song that's returning 0 results:
http://musicbrainz.org/ws/2/recording/?query=recording:%22When%22%20AND%20artist:%22Life+On+Planet+9%22%20AND%20dur:[268473%20TO%20293473]%20AND%20number:6%20AND%20release:%22Bittersweet
%22&limit=1&fmt=json
and the actual song:
http://musicbrainz.org/recording/78c84a0c-8b79-46ff-af4d-653ce52540ca
It turns out that while the changes to the database show up instantly, the indexing for search for the XML service takes at least a day, maybe less than that.
Either way, the results showed up the next day.
My goal is to find the deleted transactions during a period of the time for a list of jobs. The period of the time can be different from job to job. I am currently using TxnDeletedQueryRq but the request only provides filter on date range. I tried to look into other requests, but no luck so far. I am wondering if anyone knows a way to achieve this.
Thank you.
The only way that I can think of would be to create an audit trail report and parse for the state "Deleted". This allows you to set an entity filter for the name, plus you could set the modified date range an the report period to maybe help narrow down the information you would need to parse:
IGeneralDetailReportQuery report = MsgRequest.AppendGeneralDetailReportQueryRq();
report.DisplayReport.SetValue(false);
report.GeneralDetailReportType.SetValue(ENGeneralDetailReportType.gdrtAuditTrail);
report.ReportEntityFilter.ORReportEntityFilter.FullNameList.Add("Customer");
report.ORReportPeriod.ReportPeriod.FromReportDate.SetValue(fromDate);
report.ORReportPeriod.ReportPeriod.ToReportDate.SetValue(toDate);
report.ORReportModifiedDate.ReportModifiedDateRangeFilter.FromReportModifiedDate.SetValue(fromModDate);
report.ORReportModifiedDate.ReportModifiedDateRangeFilter.ToReportModifiedDate.SetValue(toModDate);
I have a particular saved filter that shows me all cases in a specific project and area that are active and assigned to humans (by excluding some users that don't correspond to real people but are instead used for unrelated project management operations.
It looks something like:
"All open cases in PROJECT that are active containing -assignedto:"Non-Human User 1" -assignedto:"Non-Human User 2"
I would like to amend this filter to show me the subset of these cases that have had no edits of any kind in the last two weeks. I have tried adding various flavors of the edited axis using relative time ranges as I've seen examples of in the FogBugz documentation, but I get unexpected results every time. In particular, -edited:"-2w.." or even the simpler -edited:"yesterday" shows me results where the Last Updated column says, maddeningly, "DD/MM/YYYY (Yesterday)."
(This is with FB 8, for what it's worth).
I was able to get this to work reasonably close to what I expected by adding a search axis term for edited:"..-2w" (where -2w means "two weeks ago" and could of course be changed to whatever window of time was relevant). What tripped me up is that I was trying to exclude things edited between two weeks ago and now using -edited and that didn't quite do what I expected.
Instead, my final query looks like it is grabbing things edited from the dawn of time until two weeks ago (further restricted by additional filters of course).