We are a slack partner that could create a number of workspaces. I was wondering if there was a way to create workspaces programatically. Once created, we could use the api's to create channels, etc...what was wondering about the workspace creation. Thanks!
An year old post, but still thought of answering.
check for Slack Admin API... this need to be at org level.
https://api.slack.com/methods
admin.teams.create
There is no public API for Workspace creation.
Related
I currently have a script that takes a list of people and creates new Asana projects, one for each person. These people are not in our Asana organization and need to be invited as guests to their respective projects. If I try to include a followers or members property in my API request, I get denied, and the docs list those properties as read-only.
I noticed this question from over a year and a half ago, where an Asana engineer said that it was on the API roadmap and that he hoped to publish it soon. It seems like the engineer in question no longer works at Asana, so replying to him won't help me, but has any progress been made on this front? Being able to invite guests to each project programmatically would be a huge time saver. Thanks!
We decided to keep this as a read-only endpoint. Apologies for the confusion.
You can add and remove followers on a task through the API. Perhaps you could adjust your workflow to use tasks instead of projects.
I have a TFS instance and I want all the users in corp network to be able to access that TFS link. Is there an easy way to do this other than giving each user /security group permission in TFS settings. Similarly I have a requestor field in the TFS form and I want all these users name to be populated in that drop down. How can I achieve this?
You realize that you need a TFS CAL for each user?
You can create a group in your domain where you add all users then give TFS access to that group.
How do I share artifacts (e.g diagram and docuement) across the entire project, not just at issue level at JIRA? Something like a common area for posting information.
A couple of possibilities spring to mind.
Firstly you could use the HipChat integration. Sending messages via comments to a team HipChat group.
Another option would be to create a generic JIRA user with an email address that is a mailing list for your team. That way you can use the Mentions functionality to inform everyone of something.
More about the mentions functionality here: Atlassian - Using Mentions
Use an Epic in the project
If you are using Jira Agile you can simply create an epic (called Documentation) and house all of your documents in the epic itself or group documentation by creating subtasks in the epic to essentially create "folders". To ensure the team is seeing any changes add them all to the "watchers" list.
Use a Confluence Space
If you have access to Jira Confluence, just create a project space and create or link your documents there. Another benefit of using confluence is you can make these documents available to external customers (no need of a Jira account). To ensure the team is seeing any changes add them all to the "watchers" list.
Creating a Space
https://confluence.atlassian.com/doc/create-a-space-139463.html
Use a Project Dashboard
Use a dashboard and ask that your team pay attention to this every day. Dashboards are a great way to propagate information to distributed teams.
Customizing the Dashboard
https://confluence.atlassian.com/jira/customizing-the-dashboard-185729498.html
Is it possible to assign a user to a workspace through asana API. The documentation here doesn't seem to be making any mention of it.
Is it possible to assign a user to a workspace if we have the API keys to both the asana accounts(i.e one belonging to the user and the other of the user to which the workspace belongs)
We do not currently support managing workspace members via the API, however we have made significant progress towards supporting this. We're currently weighing some security considerations, though, so it's hard to say when we'll be able to launch this. Sorry, I'm sure that's frustrating to hear.
I am in need of replicating all kayako helpdesk tickets into TFS. This includes creation of the ticket, updates of the ticket, and closure of the ticket. I've looked around and I can't seem to find any elegant solution to this. Can any of you point me int he right direction?
You can roll your own integration by building on the TFS Integration Platform.
Does Kayako support webhooks? webhooks allow you to send data when it happens, so for example when a ticket is created or when it is resolved - you can then have your application process that data. This is far better than having to make repeated calls to an API to see if there are changes to a system.