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
Related
I have an old instance of TFS 2015 that was installed with the DefaultCollection for the instance. We are moving to a 2017 TFS instance now that has a Named Instance so we can't just import the old TFS into the new because there is not DefaultInstance and there won't be one (according the to the SysOps that run the server). So I connected to the 2015 instance and ran a query to pull down all the work items and history into an excel database. However, when I try and connect to the 2017 instance to Publish I keep getting the error:
The reconnect operation failed because the team project collection you
selected does not host the team that the document references. Verify
that you selected the correct team project collection and try again.
So how can I pull the DefaultCollection from the old 2015 server and publish it to the new 2017 TFS server under a different Collection Name?
Thanks.
I finally figured out how this is done so I am posting my steps in case someone else needs to know.
Created the queries in the old version of TFS (in my case 2015). In my case I created a "Tree of work items" query type, and set the Work Item Type value to Feature. And Set the State to any.
In the "Filters for linked work items" set the Work Item Type value to [Any]
In the Filter options, set the option in the dropdown to "Match top-level work items first" and the Type of Tree to "Parent/Child"
Run the query and look at the results. The minimum columns that I found to work are Work Item Type, Title, State, Area Path and Iteration Path
Run the query in Excel to set the results. Copy the results from the excel worksheet. Open a new instance of Excel, and connect to the new instance of TFS. Select New List, then change the type to Input List.
IMPORTANT!
Make sure the columns match between the two workbooks. If you have a Column called Title 1, Title 2, Title X then click the title column and click "Add Tree Level" to create the same columns.
2. Paste the results into the new worksheet. Change all the values in the "State" column to "New". Any other value may not import. Make sure to update the Area Path and Iteration Path to the correct values.
The minimum columns I found that do the correct import are:
1. Work Item Type
2. Title
3. State
4. Area Path
5 Iteration Path.
When I tried to import the Epics with children it would constantly fail. So I did the export with children from the Features down to stories and tasks/bugs and it worked.
I am kinda new to SharePoint and I have to create a very simple WF, but that actually I am not able to do it through SharePoint Designer.
I have got a document library, where users upload some project request, and a list of customers. When a new project request is created, this is associated to a customer of the existing list. Each customer has got some data, like a column for Project Manager and another column for Technical Supervisor. I have to create a WF where the Project Manager and the Technical Supervisor get an email if a project of their own customer is created or modified.
I tried using a List WF at first, but then I thought it could not act outside of my document library, but even using a Site WF it seems I am not able to let it gets data from the list.
Anyone could explain to me this Step-by-Step?
Thank you so much
So you have two lists:
List 1 - Project Request Document Library
List 2 - Customer List
This list has columns like Project Manager, Technical Supervisor and Customer Name?
The way that I would do it is to add a Lookup column to List 1, that looks up the Customer Name Column from List 2. In the additional fields part, bring over any other fields that you want too (Project Manager, and Technical Supervisor).
This will allow you to show the following in List 1:
Project Request Document | Customer Name | Project Manager | Technical Supervisor
Then create a workflow on List 1 - go to List > Workflow Settings > Create a Workflow in Sharepoint Designer.
Give the workflow a name, then type 'email' choose 'Send an email'.
Click on the 'these users' link - then click the little Address Book near the 'To' field.
Select Workflow Lookup for a User >
Data Source: Current Item >
Field from Source: Technical Supervisor or Project Manager >
Return field as: Email Address
Publish the workflow, then there is one final step to do.
Click on the workflow name in the left panel and in the 'Start Options' panel on the right select:
Start workflow automatically when an item is created
Start workflow automatically when an item is changed
Save, then publish and you're done!
I have a very simple workflow which creates a log, sends an email to a user to preform a task when the item is created then sends a different email to an external address at the same time. A field is updated using the set field in current item and another log is created.
When I enter the first item in the list the work flow starts but when the second item is created the workflow fails with the following response "The workflow could not update the item, possibly because one or more columns for the item require a different type of information"
I am using Sharepoint 2010 Foundation and Sharepoint Designer 2010. I have searched everywhere and even tried inserting 1 minute pause after the first log but it doesn't help.
I have an InfoPath form that, when submitted to a SharePoint Form Library, also adds a single item to a Task List. Each item in the Task List contains a People field that may contain multiple names. I have code in the form that creates separate items in a Custom List, one for each name in the People field.
When I manually update the Status field in a Task List item, I would like a SharePoint workflow (I'm using Designer 2010) to update all of the Status fields for the corresponding items in the Custom List. The "Update list item" option in ShP 2010 workflows will only update a single list entry. Is there a way to update all of the Custom List items that correspond to the Task List item whose Status is being modified?
To update multiple list items simultaneously, use SharePoint batch update. Look at following links for more information:
MSDN - Visual How To - Batch Updating List Items in Windows SharePoint Services 3.0
http://apmblog.compuware.com/2009/01/20/sharepoint-using-batch-updates-to-speed-up-performance/
You can also use batch operations for inserting and deleting.
I have written two workflows on codeplex - one is https://rwomi.codeplex.com and one is https://umlisdw.codeplex.com/
We've created a pretty standard issue tracking system based off of SharePoint's template with just a few extra columns. On the list view (AllItems.aspx), the first column is called "Issue ID" and has a number. Our developers and QC use that number in discussions. However, that number doesn't seem to want to show up on the detail form (DispForm.aspx) nor in the alert email.
Can this field be included in at least one of these communication methods? If so, how?
Thank you.
We did something similar and used workflow via SharePoint Designer to copy the ID field into a field called "Issue Number". The workflow gets triggered automatically on Create / Edit (we included edit because the field can be modified by the user on the edit form and if that happens we want the number refreshed with the actual ID).
Before you create the workflow in SharePoint Designer, you need to add a column called "Issue Number" to the list you want to tweak.
List item
Open Sharepoint Designer
List item
Click File New -> Workflow
Give a name for the workflow
a. select the list from the dropdown
b. Uncheck Allow this workflow to be manually started and check automatically start on new and change then press Next
Give the step a name like "Assign Issue Number"
Create a Condition
If Compare a field -> If Issue Number not equals Current_Item:ID
Create an Action
Update List Item -> Set Issue Number to Current_Item:ID
Press Finished and test out by creating a new issue.
*The Issue Number will appear on the form and if you have emails setup to notify on assignment it will appear in the reassigned template.
*It will not appear in the created email confirmation because the workflow gets triggered after that email was executed.
I just added the issue ID using a total of 4 characters. Create a new column, set it to a Calculated column, in the formula type [ID]. Voila! The ID is now in your detail view.
The ID link returned the for me, however, the work around which sufficed for me was to enter 'Created' in the Calculated Column formula and ensure it is set at date and time. That then creates a unique idenity (unless you receive more than 1 list update per minute) than can be viewed in the email alert message