Quire how to add a task to a board and a board column with your API, i can manage to create tasks but can't assign them to a board with your API.
to add a task to an existing board set the board property of the PUT /task/{oid} action
to add a column use the addColumn property of the PUT /board/{oid} action
UPDATE:
to place a task into a specific board column you have to set the task status corresponding to the column value (e.g {"status": 10}) PUT /task/{oid}
The task will then 'jump' into the matching column of your board
Related
I would like to do changes to my work items automatically when working in Kanban board. For example, if I drag work item type to other column (changing Board Column field value) - I want to place a tag saying it's current Board Column value.
This is currently not available in Rules settings for work item types.
Where is the best place to put ADO Boards enhancement requests?
Your requirement can be achieved by alternative. Generally, when you drag work item type to other column, the state filed is changed too. So you can create a tag filed and add rules to set tag value when state changed. Check the following steps:
Create a tag field:
Create rules for each state changed. For example:
By the way, if you have new ideas, you could submit suggestions at website below:
https://developercommunity.visualstudio.com/content/idea/post.html?space=21
I am having backlog in TFS 2018 and I am using default template provided to create the tasks.
The template is having the 'Activity' drop down, while selecting the 'Activity' it is also renaming the Task Title. It is ok if I am adding the task using TFS.
Now, I am using the Excel to create the tasks in the user story.
Only problem is whenever I publish the list, it is renaming the Title of the tasks with Activity name.
For example, If I publish the following list, "My Task" will be renamed with "Requirements- Review" (Value in Activity Column) in TFS board under "My Userstory".
Is there anyway to disable this behavior while adding tasks using the Excel?
As per my understanding both Titles are required as it is creating the
Parent Child relationship. In Excel I am selecting Title 1 and
clicking on "Add Child" and it is creating Title 2 column.
Actually we do not use this kind of way to add a nested list of work items( Parent Child relationship)
For example, you should first convert your flat list to a tree list by adding a tree level.
Enter titles for backlog items under Title 1 and for tasks, under Title 2. Also, select the corresponding work item type for each. Here we specify Task.
Publish your worksheet and the ID 95 is new created through Excel. In the background, parent-child links are created for each task listed.
As you can see in web portal, the new create task is list properly and title do not change and activity is also right.
More details please take a look at this official tutorial-- Bulk add or modify work items with Excel
I'm creating a WF with SharePoint designer 2013.
The work flow should be approved by 3 company members. So, I added a new column to my custom WF task list called "Approval stage" which is a choice column and should has values "Analyst, Reviewer and Manager".
When assigning a task for each user, I need to set the value of this column.
For now, I can update it only after the task is finished (approved or rejected). But I need to set it in the assigning process.
How can I do it??
When you create a task you will get an output as an ID on the basis of that you can update the field related to that task item.
I have a multi-step Sharepoint workflow in task list A that starts when a new task is created in that list and creates a task in another list, B. When that task in list B is completed, I would like the workflow in list A to create another task in list C.
I am using Sharepoint Designer 2007 to build all of this and at the moment I have this represented by multiple steps. So, step one is to create the task in the other list, and store its ID as a variable. Step 2 is conditional on a value in the task created by step one being marked complete, and it creates a task in the next list, and so on.
However, when I run the workflow, it marks its status as complete as soon as the item in the first list is completed, and does not go on to create the task outlined in Step 2 of the workflow.
I would like to know why the workflow is marking itself complete at the end of step one, and why the subsequent steps are not executed. Thanks in advance for your help.
I feel some problem with your logic.
You should have two workflows for doing this task
Workflow associated with list A to create a task in list B
Workflow associated with list B to create a task in list C
I shall explain it step by step.
You need to create a hidden field in List B to store list A's ID
Create a workflow associated with A on item creation for creating new item in B and copy the A's ID in B's hidden field
Create another workflow associated with list B for creating new item in C. You can get the A's record by comparing the A's id field with B's hidden field
I have added a workflow to a SharePoint(2007) calendar. The workflow copies information from Column A to Column B if Column A is not equal to Column B. I set this workflow to start when an item is created or modified. However, I would also like to start this workflow on all items that already exist in this calendar.
Is there a way I can do a mass start and run the workflow for all the items that already exist?
EDIT: Let me clarify my question a little more. I would like to run the workflow one time on the 200-300 items that have already been created. I don't need to traverse the items everytime a new item is added. Just one time to compare/copy Column A to Column B for all the existing items
Here's a low-tech method that should work. Go to the All Events view for the calendar, click Actions > Edit in Datasheet, then make an edit quickly to all event rows. Since it's a pseudo-spreadsheet view, you can set a value in the first row and then fill down all the rows. That would quickly modify each event, and thus should trigger the workflow.
If you don't want to edit an existing column (and lose any valuable data, for instance), you could just create a new column temporarily, go back into the datasheet view, and set a value in that column for all events. Once the workflows have been triggered, you could then just discard that column.
Add a customaction to the list's action panel through a feature that when clicked traverses all items matching the description (Column A != Column B), then triggering the workflow through the SPListItem's WorkflowAssociations