I need to select a user and then list all the projects that the user is working on. Also how can this be done with a specific workspace of the user? What would the url look like?
Also how do we access the teams that are created in asana using the asana api?
The documentation is decent.
Most notably, you're probably looking for endpoints /users, /projects, and /projects/[project-id]/tasks. To the best of my knowledge the API provides no way list all the projects a user is working on. You have to create that list yourself by iterating through all the tasks on a project.
Related
I am looking to make a REST API call to Jira to find:
A list of projects I have access to/can view
Ideally, what specific rights I have in each project
specifically for myself. How would I do this?
With my company this might be a long list, so conceptually, is there a level of global permission in Jira that would allow me (at least read-) access to all projects?
I don't want to create a slack app, but I would like to write a script that - given a list of workspaces - can get the number of members in each workspace. These would be public workspaces like popular open source projects. I've tried combing the slack APIs but they are mostly geared around how to create slack applications as opposed to getting data like this. Would appreciate any help!
I am afraid that won't work. The Slack API requires you to first get a valid token for a workspace before you can get any information about, e.g. number of users. This usually happens by installing your Slack app, e.g. from the Slack Directory.
I am using POSTMAN collections to test my API before opening it up. I work with a team of developers and we would like to share/add/edit our collections amongst each other.
Doing this in source control is proving slightly tricky as can be seen in this comment on the GitHUB page:
This issue still persists in Version 2.1.1 (packaged)
The order of requests might be deterministic now, but the diff of an exported collection from two different machines and users includes data that are not related to the collections exported. The diff is full of owner and other id conflicts if there are several people working on the tests at the same time.
What is the best way that we have of putting this data in some sort of version control system? Any suggestions otherwise?
Putting it in a VCS undoubtly will give you some headaches as you mentioned. Your best bet is to use Postmans functionality to share collections. Here is from the documentation found at https://www.getpostman.com/docs/sharing
Starting with Postman v0.9.3 you have the ability to share and manage your collections more effectively. The first thing you will have to do is create a Postman account. You can create one using your email ID or a Google account. Once you are signed in after creating an account, the collections you upload on Postman are linked to your account. You can delete them later through the "Shared collections" item in the navigation bar dropdown.
Collection v2 format removes most, if not all, problems with portability.
http://blog.getpostman.com/2015/06/05/travelogue-of-postman-collection-format-v2/
The format must be highly portable so that it can be easily transported between various systems without loosing functionality.
Source Control in Postman
The question about sharing collections so that you can collaborate with your teammates has been answered a few different ways, as described in other answers of this question such as by sharing the collection or by syncing to a team account.
Version Control in Postman
The other part of the question was about putting the Postman data into a version control system. Postman introduced some version control features for the paid team accounts, like being able to restore collections to a certain point in the activity feed.
The paid team accounts also get integrations to sync their collections to their own version control systems like GitHub for example. If you're on a free account, you can use the Postman API to build your own similar integration to update the collections.
This blog post talks about some of the version control features in Postman.
UPDATE: Postman released forking and merging in Postman app v6.7.1 so you can manage version control in the app.
To automatically share your existing postman collection you can use Postman Pro.
It is a paid service provided using which a team lead can purchase the complete pro- scheme for his team and work as an admin.
Postman pro enables the following and many more:
Any changes in the API are automatically reflected in Postman for all member
Members subscribe to the collections from the Team library and get notifications of any changes.
For more information you can refer:
https://app.getpostman.com/dashboard/team-upgrades
This is what I use with my team of automation testers.
What is the best way to manage users with PirhanaCMS?
I would like to prevent some users from adding content (posts etc...) in some categories and prevent that some sites be listed for some users. (For people who don't know it, PirhanaCMS is a micro CMS programmer oriented).
I would like to use the sites features because I'm working on a project in which I'll have a "network" of several sites managed by different entities of an organization. I would like that each entity be only able to see its own site but that the big organization at the top be able to manage every sites. Moreover, within a site I would like that some users be only able to edit some part of the site.
Are these features built-in ? Otherwise what is the best way to implement them myself around the CMS ?
I am using ASP.NET MVC 4 and EF5.
If you take a look at System > Permissions in the manager area you can see that there are permissions you can give to groups for different parts of the manager interface.
There's however currently no built in support for restricting access to different site trees, but you are free to add a feature request for this at GitHub or maybe participate by implementing it and sending a pull request!
I've created a couple of dashboards in my rally environment and since I cannot make them project viewable I would like to share the dashboard without sharing it with the entire workspace.
Is this possible? If so how?
Unfortunately, shared pages in Rally get shared with everyone and cannot be set to be visible at the project level. You will need to share with the desired users which apps and settings (or code if it is a custom HTML app) you are using in order for them to be able to re-create these themselves.
You could always post this as an idea at https://ideas.rallydev.com to get visibility for the functionality you are looking for.