I am coding an "Asana Post" program but I need to give the user the option to choose the Project to post the task to.
But obviously, I can't offer the user to post to all projects as they may not be a member of all of them.
The only option that I see in the API is to pull all the projects with their Team IDs and then to pull all the Users for that Team and check if he is a member.
That seems very tedious.
Any other ideas?
Related
I am building an application that creates Teams for my training classes and I can Create a Group, make it a team, and then add the required folks to the Members list. I want to be able to differentiate between "students" and "facilitators" for reporting and management.
I have found /api/v1/teams/{0}/memberTags/ but I don't seem to be able to call it directly or find it in the SDK documentation.
Is this API available?
Teams Tags are currently in the Graph beta
https://learn.microsoft.com/en-us/graph/api/resources/teamworktag
Tags provide a flexible way for customers to classify users or groups based on a common attribute within a team. For example, a Nurse or Manager or Designer tag will enable users to reach groups of people in Teams without having to type every single name.
Tags are scoped at the Team level.
When a tag is added, users can #mention it (#tag) in a channel in that team . Everyone who has been assigned that tag will receive a notification just as they would if they were #mentioned individually. Users can also use a tag is to start a new chat with the members of that tag.
No, there’s no API for this now .
Check here to Manage tags in Microsoft Teams app. We will keep you posted once this feature is available through API.
My boss come with a very unique requirement, below is the explanation.
Imagine there is 10 user for a particular project team.
And the work flow is like
Documenting -> Review -> Publish
Now, the requirement is like below.
If I create Ticket with Summary "Version 1.0 Documents" with the above explained workflow, then it should also allow us facility to manager for user regarding each state of workflow like
Documenting assign to User A
Review Assign to User B
Publish Assign to User C
Note: I know I can assign ticket to individual user while changing state, but I want something pre-planned so as soon as I change status of ticket it will automatically assign to user.
I know I can do this using post action of transaction but what I want is, the assignee should be specified at creation of ticket as the same workflow going to use by many project and ticket, and every project will have different team
So , I need something add-on which allow me to manage team for each ticket.
Also, User C should be able to see his/her upcoming work if ticket is in any previous state i,e Documenting or review.
I suggest you should create account role for this and group to each department/team for their flow. you can use account role for separating their works then the department/team is useful for which members/users can see the particular issue/ticket. we already build something like this we have 3 account roles each ticket so i can say this is possible. if you still have question just let me know thanks.
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.
Not exactly like this - How to publicly share a Visual Studio Online Repository? - I am trying to share the source code repository (Git) from Visual Studio Online to registered stakeholders. They need to get at the latest stuff at the Master branch to eval it along with work items. How can I do that?
Thanks.
If you have people with a Stakeholder license they won't be able to see the code. The Stakeholder license only gives access to:
View team dashboards and portfolio backlogs
View, add, and modify items on the backlog
View, create, and modify work items such as stories, features, and bugs
View, create, and save queries
Create and receive alerts when changes are made to work items
Submit, view, and change your feedback responses.
For people to see the code, they will at least need a Basic license. If you then want to restrict their access, you can do so by creating a TFS Group and setting the correct permissions. In this case, you want to limit the Code permissions to only Read so they can't modify the code.
See Permission reference for Team Foundation Server for more information.
This means there is no free way to allow users to read your code. You do start with 5 free basic licenses however, so if that's enough you can assign those to your users.
Just started on Asana and liking it. A couple of queries -
Is there a way to check history (log) on Asana Tasks and Projects. Say i want to check if a task has been accidently removed by another person.
Can I assign a person just the view rights on a project and not edit rights.
You can check the activity feed of a task via stories: https://asana.com/developers/api-reference/stories
We don't currently have read-only rights.