Asana Projects API Not Returning All Projects - asana

We are experiencing an issue where we are requesting all projects from a workspace, but, only 29 projects are being returned. Many are missing. This is the code we are using: https://gist.github.com/dzoba/921ec35073d6329aecadc08ceacb445e
This is the list of projects we are returned:
https://gist.github.com/dzoba/4a57a61849c2bdf3c610aa6d02082482
This is an image of some of the projects for this Workspace. (I've removed all last names). If you compare you can see many of the ones that end in " - Marketing" are not returned by the API.
How can I get all projects from a workspace, and why aren't all being returned?

Turns out this was because the account that created the API access token was not a team member of the teams which contained these projects. We made that account and admin and a team member, which fixed the issues.

Related

TFS 2017 Variable Group shared between projects

Using TFS 2017 Update 3, we've defined a variable group in project A, security is setup to share with "Project Collection Valid Users" as "User". When trying to Link Variable Group from Project B, the list is empty.
Link Variable Groups
Any idea?
Note that I've also configured security directly on my user account which is team member of both projects... no success
Microsoft documentation does not contain any sharing information: https://learn.microsoft.com/en-us/vsts/build-release/concepts/library/variable-groups
You can't. Build and release definitions, along with all associated stuff (like task groups and variable groups) are scoped at the Team Project level. This is one of many reasons why it's recommended to keep everything within a single team project.

TFS - User can only see certain branches within a Team Project

I have set up security in TFS 2012 Team Projects. There is one user who can see parts of a Team Project (certain branches) that he otherwise should not see. I have checked the branch security as well and can't find anywhere why that user should have access to it. It also shows a weird plus sign in front of that Team Project for that user only where he can only see some branches and not the full team project.
figured it out. apparently user had checked out some files before we restricted the permissions and therefore once the user checked in their changes, they could not see these projects anymore.

Adding a new account in Team Foundation Server

I have a problem with adding of new accounts into Team Foundation Server 2010. I can add a new domain account into group Contributors of my team project without problems but after that I can't see it in the list of available accounts, for example, in the drop down list 'Assigned To' at a work item page.
The added user can see the project, do check-in and check-out but he can't get access to the project work items. He has got an error
TF201072: A user or group could not be found. Verify that the users and groups used in your work item type definition have been added to Team Foundation Server.
Can anybody help me?
First, make sure that you have the latest version of TFS. There have been many bugs fixed over the years and years since 2010 and you would be best servers to upgrade.
You should check the status of the TFS jobs, with the tfs Admin Pack:
http://blogs.msdn.com/b/granth/archive/2010/07/12/administrative-report-pack-for-team-foundation-server-2010.aspx
Is that user licenced?
we've got a tfs_member AD group which we've added in here:
http://yourtfs:8080/tfs/_admin/_licenses
to sort that out. The user has to be in that AD group and be in the project's contributors to show up .

TFS 2010 Permissions. All user have all right

We have a TFS 2010 with 14 collections. Each collection has its own team members (different Active Directory Accounts).
When a user logs into TFS, is seeing all the collections, he can enter the draft, create work items, see the source code, etc.. So he is not in the list of Team Member.
I made a program in c # to go by collection and project permits and no one is repeated.
How I can diagnose this behavior? There a tool to enter the user's name to show me why he has those permissions and how inherited (collection groups or groups of server).
I appreciate your input.
UPDATE:
Thanks you for the answers. We solved. it was a sync problem between Active Directory and TFS.
You could try http://tfsadmin.codeplex.com/ I don't believe it has the user lookup function but I've found it a lot easier to edit roles with than using TFS itself.

Can I Populate a TFS Dropdown with Project Members Only?

I have a TFS 2010 Work Item Type with a custom field called "Requested By." This field can be populated with any name, but since most of the requests come from project developers throughout the organization, the SUGGESTEDVALUES property should populate the dropdown list with members of any TFS team project.
I have tried various values for SUGGESTEDVALUES, but both Collection\ Project Collection Valid Users and Server\ Team Foundation Valid Users seem to return every valid Active Directory account—well over 10,000 names.
I recognize that one option is to add an ALLOWEDVALUES item with multiple LISTITEM entries for Project\ Contributors for every team project, but with more than 150 team projects in the organization, this would be time-consuming initially and challenging to manage in the future.
Is there any easy way to populate the drop-down with TFS valid users who have actually been assigned to any team project in the collection, and exclude "Valid" users who exist in Active Directory but have never been assigned to a project?
What do you get if you use Project Collection Valid Users?
Project Collection Valid Users is the correct group to use, and I have entered it correctly.
However, one project team wanted to make their code available to the entire organization, and added ORG\Domain Users to the [Project]\Readers group. This was discovered by running a full audit with TFS Projects based on a hunch that something like that must have happened.
Having answered this question with "because a project team was doin' it wrong," I have posted a follow-up question to find out how to correctly grant all valid TFS users access to a specific project. See How can I grant Team Project access to all Project Collection Users? for the discussion on (hopefully) doing this "the right way."

Resources