Asana typeahead endpoint returns all projects for Personal Projects workspace - asana

When using the typeahead endpoint to search for projects in my Personal Projects workspace, it returns all of my projects. The results don't change for different queries and the count parameter is ignored. I don't have this problem for other workspaces/organizations. Is this expected since Personal Projects are special or is this a bug?

(I work at Asana)
To answer the question, yes it is a bug. But also, in general you can expect issues when dealing with Personal projects as they are indeed special.
We've addressed the filtering issue and the results you get should be filtered by query (required) and count (optional) now. Thanks for reporting!

Related

Using the BitBucket 2.0 API, how can I query commits from a specific user/author?

I'm looking to fetch all repo commits from a specific user/author and I can't quite get my head around the filtering documentation from Atlassian.
Entering this in my browser (with the placeholders changed for my project) lists out 30 items from my project.
https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/commits
But I want it to list out only the commits authored by myself. I've tried all sorts or variations like:
.../commits?q=reviewers.nickname+"marknotton"
.../commits?q=user+%3D+"marknotton"
.../commits?author="marknotton"
Every variations just returns the same results. My url params are ignored, presumably because they are invalid. This could just be a silly syntax issue? Are there any examples I could refer to for help?
https://api.bitbucket.org/2.0/repositories/{workspace}/{repo_slug}/commits?state=merged&username.1=marknotton&role.1=AUTHOR

JQL to get blocked Issues

Is there a native JQL (not a plugin) that returns tickets that have linked issues listed as "is blocked by" (so I can see all my blocked tickets).
All I have found is linkedIssues() but that can require a specific issue ID to search for which is entirely unhelpful.
I am using Jira Cloud 7.4.
In the core JIRA JQL functionality the closest thing you have, as you've already found out, is linkedIssues() that requires a parent Issue reference.
What you need is Adaptavist ScriptRunner, they have a function called hasLinks(). There are also a handful of other add-ons that offer this functionality but like ScriptRunner, they all cost money.
Related JIRA community question
JIRA Cloud feature request
The below query is also helpful (add it in the filter setup):
project = "Project ID" AND issuetype in (story, Spike) AND Sprint = "Sprint ID" AND linkedIssue in issueHistory()
According to Esther Strom's answer on this Atlassian site, there's a new query type:
Atlassian has very recently introduced a new JQL function called issueLinkType, which can be used in filters, but also in boards.
It's not perfect; if you're already using card colors for something else, you won't be able to use this as well. It also behaves inconsistently when a ticket has links of multiple types. But if you're looking for an easy way to get a view into what might be blocked, and what might have blockers, it works pretty well.
In KQL you can specified the type of link.
For what you want to do here what you can use
issue in linkedIssues([Issue#],"is blocked by")

MS Graph API GET Group members only get users

Currently i have a request for getting the members of a group. But can someone help my composing a request that only show objects of type microsoft.graph.user so i don't have groups in my group members request?
The current request:
https://graph.microsoft.com/v1.0/groups/GROUPID/members?$select=id,displayName,givenName,mail,surname,userPrincipalName
The standard way to achieve your requirement would be to apply type case such as https://graph.microsoft.com/v1.0/groups/GROUPID/members/microsoft.graph.user?$select=id,displayName,givenName,mail,surname,userPrincipalName. There is currently a bug that fails the above query. Please use query like https://graph.microsoft.com/beta/groups/GROUPID/members/microsoft.graph.user in the meantime as a workaround. Notice the changes in version from v1.0 to beta and the lack of $select. We will soon fix the bug to get the former query working.

TFS OData - get work item types

Is there a way to get all Work Item types for a project via tfsodata.visualstudio.com?
In documentation: https://tfsodata.visualstudio.com I was not able to find anything about it, and it is hard to imagine that something so important is not implemented.
Any help appreciated!
No such OData API to get the list of work item types. It's suggested to use REST API if you use TFS 2015 or VSTS:
GET https://{instance}/defaultcollection/{project}/_apis/wit/workitemtypes?api-version={version}

Jira to know how many poeple have visited an issue

I want to know how many people have visited a particular isssue in order to know its popularity( I can't trust on number of watchers of the issue) .Is there any way (JiraDB or anything) by which i can know how many people(just the count) have visited any particular issue.
The question can be modified like this : Top 10 mostly visited issues in a week or so.
Seb's earlier answer provides a possible solution for JIRA Cloud. I am not aware of any off-the-shelf product for behind-the-firewall installations of JIRA, and I do not believe that views are tracked anywhere in the JIRA database.
For behind-the-firewall instances, you could certainly write a script to parse the JIRA access logs (stored in $JIRA_HOME/logs/access_log*) to count issue accesses that way.
The JIRA access logs are stored in a format that is similar to the Apache access log format, so you just need to parse out accesses to individual issues by looking for URLs of the format "http://MYJIRA/browse/ABC-123".
Out of the box this is not possible. Jira does not log view counts for single issues.
You could have a look if there is any plugin for this at https://marketplace.atlassian.com/search?application=jira
E.g. https://marketplace.atlassian.com/plugins/communardo.connect.usage.statistic.addon looks like it could fit your requirements, but I personally have never heard of it.

Resources