I'm interested in using Graph API in order to manage tasks within MS To do. I've already found documentation for creating a new task.
However, I didn't find anything about the following during a new task creation or task update:
Is it possible to set subtasks on a task?
Is it possible to set a category on a task?
Is it possible to reassign a task?
Maybe someone has information about it.
As of now there is no way you can create sub-task with Microsoft
Graph. There is a feature request already present
here,
please upvote it so that product team may consider it for
development in future.
For category as well we cannot get or set the data as of now. For
this as well there is a feature request
here.
Please upvote it.
For the assignment as well there is a uservoice
here.
Please upvote it so that it may be implemented in future.
Related
Trying to determine who created an Asana task from the API, but:
There's no author field on the task itself.
Followers cannot be used because the creator can remove himself from followers.
Looking at the stories of a task, there is not system event for creation.
The best I've found is to use the created_by field of the first (eldest) story of a task.
Is there a better alternative?
This field is not currently available on tasks, your approach (look at first story) is the best practice at the moment. We'll take this into consideration for future API improvements.
I would like my stake holders to be able to vote on user stories or features in TFS 2013 (or 2015 if this is coming?). The end result is so I can see how much interest there is in a given idea and help prioritize work. This seems like something that should already be implemented but I am not sure what this is called to be able to properly search for it.
Is this a feature in TFS?
Can I extend TFS to do this?
Or is there a 3rd party product that can integrate with TFS and provide this?
Thanks
You can integrate with uservoice to do this. There is a feature called service hooks that allows you to trigger the integration with them and it allows you to do the same as http://visualstudio.uservoice.com
You could also extend TFS to do it yourself with a simple voting webpage and a single numeric field.
Or you could do a "hot or not" implementation to provide that data as an alternative.
Do you plan to add possibility to retrieve (via API) all tasks from project including those which are archived?
(I work at Asana)
That would be a useful feature and we are already planning on adding it. However, I can't comment as to when it will be possible.
Until the API officially supports this, you can always query /tasks?completed_since=now to get only incomplete tasks, then query /tasks, and filter for tasks that only appear in the second list.
Archived tasks can be accessed by including the parameter ?include_archived=true in your request for querying tasks by project.
Task section in Asana documentation
I am trying to do this exact same thing as well. We are using a project to track line down events on our manufacturing floor. I found this post helpful and you can append “?include_archived=true” to your query but I found out that you can also do a reverse lookup on tasks by their tag. This will also show achieved tasks as well.
I've been looking for a way to have a user acknowledge a
ticket after it has been assigned to them. I don't know if
this is a built in feature or if there is a plugin that
will create a state/button for a user to accept a ticket
after it has been put in there queue. I would expect to
see something like this from the ticket window around
workflow or start progress but no amounts of digging
through configuration settings has turned anything
relevant up.
Does anyone know about this added functionality in JIRA?
Much thanks.
I did this by a custom workflow step. After an issue arrived to an assignee (with status New) he/she should move it to another step (with status Open). Until he/she does it, the issue is considered as not noticed/reached the assignee. Also I have had a report showing issues with New status for more than a predefined period of time.
I'm not aware of a ready-made plugin which performs similar task (perhaps, I should dig into my posts on Atlassian answers to discover some clues for other solutions).
As #Stan says above, a custom workflow is the way to implement this. The workflow functionality in JIRA is very flexible and as a result has a bit of a learning curve, but Atlassian's documentation is pretty good. Post back here if you need help.
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.