I need to copy the wokritem tree, Like for example :
Feature- Userstories- tasks
While copy the feature, I need Userstories under feature and Task under Userstories
When I am trying to do " create copy work item" its copied feature and users Stories not task.
Related
I'm using TargetProcess (scrum) to manage our projects and encode timesheets.
So I made a tool to extract all needed data from targetprocess to an excel file, then import this excel file to our MSProject file to update all data.
Everything works perfectly except one thing :
In the Import Wizard, as I want to update my MsProject file and not create a new one, I select the "Merge the data into the active project" option. I've an ID as "Merge Key".
The structure is :
Project
Epic
Feature
So I've 3 Levels.
When I do my import, if I've no new epic or feature, everything works correctly, all my data (time, complete, date, etc) are well updated.
But if there is a new Feature (for example), this new feature is append to the end of my MSProject file and it not placed in the correct project.
So for example, if I had :
Project_A
Epic_A1
Feature_A1a
Project_B
Epic_B1
Feature_B1a
and if I add a new feature "Feature_A1b" in the epic "Epic_A1" of project "Project_A" in TargetProcess (or the excel file used for import), the result after the new import (merge) will be :
Project_A
Epic_A1
Feature_A1a
Project_B
Epic_B1
Feature_B1a
Feature_A1b
instead of :
Project_A
Epic_A1
Feature_A1a
Feature_A1b
Project_B
Epic_B1
Feature_B1a
I tried to define the "Task Summary Name" in my excel file, and bind it to the "Task Summary Name" field in MsProject during the import, but MsProject don't care about it.
Is there any way to tell MsProject to append the new feature to the correct project and not at the end of the file ?
That is correct--when the Import Wizard is used to merge data, new tasks are added at the end of the schedule.
The way around this is to avoid having the Import Wizard add the new tasks. Instead, before running the wizard, add placeholder tasks where you want the new tasks to go and update your merge source file with the Unique IDs of these placeholder tasks (presuming that's what is used as the primary key).
Is there a way to clear an input field in a task every-time the source directory/repository is changed?
Context:I am developing a custom VSTS task, and in it I have a input field type filepath.
I would like to clear the input field in my task every time the user changes the GetSource or Repository.
Existing behavior in "Copy Files to:" task:
eg: Consider in Get sources -->select a source I have selected GitHub, and a repository out of my account.
In the "Copy Files to: " task , input field "Source Folder" I go ahead and select a folder from my Repo (Browse Source Folder--> Select path).
If I return to the GetSource and change the "repository" or "selected source", then this input field in the "Copy Files to: " task is not relevant anymore. But it remains the same. I have to manually clear the field.
I would like to have this cleared automatically.
Is there a way we can accomplish this?
I checked the azure pipelines tasks samples and the task schema but did not find such a way. If you would like that feature, you can create a request for this feature in developer community.
That will allow you to directly interact with the appropriate product group, and make it more convenient for the product group to collect and categorize your suggestions.
I have multiple release pipelines using similar set of tasks. I have created a task group as explained in Task Groups. I want to reuse this task group in other release pipelines.
I cannot find any task/menu item in Azure DevOps to do so. Documentation in Task Groups mentions exporting the release pipeline as json but the import section is not quite illustrative.
If you created a task group and you want to use it in another releases, just click on the + to add a task and in the search field start to type the task group name (for example TaskGroup1), then choose it:
I had the same issue and could not find my Task Groups. What fixed it was:
Under Pipelines, go to Task Groups. There you have an Import button where you can import the json Task Group file. When this is done, the Task Group became selectable when wanting to add a new Task.
Hope this helps :)
You need to search for the name of the Task group in the search box while adding a new task and not "task group".
If you created/imported a task group with name MyCar.FrontendApp, then in the search box for add a new task put "FrontendApp" and add that task.
In case someone else will have this issue and will come to this thread: even after import and save new task group may not appear under Add task section. In this case try to click Refresh link on the top - it should fetch all changes and update the cached tasks list:
I imported a TFS query to excel to add a bunch of tasks. That part worked well. Now I just need to attach them all to their appropriate user stories (parent). I tried a bunch of different options in "column options", but none of them let me choose the task's parent. Is this even possible through excel?
You can achieve that by adding parent/child linked backlog items and tasks, please see Bulk add or modify work items with Excel for details.
In you case, you have bulk added the tasks to project,you need to link parent user stories by following below steps:
Select any task and link it to its' parent story (to generate the tree level title in query).
Create a Tree of Work items query like this:
Open Excel,New list > Select the created query above > OK
Edit the query in excel, move the Tasks title from Title1 to
Title2 accordingly based on their appropriate user stories.
Click Publish, check the Parent link in backlog.
A little background: I work for a company that produces a product that has a workflow for projects with many "concurrently" running tasks. For this discussion, lets say that Project A creates 4 Sub-projects.
Both the main project and the 4 subproject workflows will create tasks in the main task list. The main issue that I am having is how to associate the tasks created by the subproject workflows back to the main project.
For instance:
Project A is created in the Projects list. This list has ONE workflow associated with it called "project start". This workflow is a manual start workflow which when started then creates the four subprojects in a subprojects list - these subprojects need to run concurrently hence why I have created them in a secondary list with their own workflows. The subprojects list has 4 workflows associated with it to manage the 4 subprojects - each of these "auto-start" when the subprojects are created in the subproject list.
So anyway, to save some typing I will refer to the subprojects as UNITS 1 - 4.
I create Project A and manually start it's workflow. The project start workflow creates the Unit 1, Unit 2, Unit 3 and Unit 4 items in the subproject list (at the same time because, as I said earlier, these items need to run concurrently). Each of the unit manager workflows start and begin creating their to-do tasks in the tasks list. I am using the "assign a to-do item" task activity because all I need to know for the workflow to progress through it's steps is whether or not the work is completed.
Once all 4 Unit workflows have completed, the Project Start workflow will now begin to manage the final portions of the project prior to completion with additional task items (manager approvals and so on).
Now the issue I am having is that the view I have set up for the task list shows the "title, start date, end date, completion status and link" columns. The link column shows a link that refers back to the creating list item. For this example, the Unit 1 manager workflow operates on the UNIT 1 item that was created by Project A. So for "example task 1" that was created by the unit manager workflow, the link is "Unit 1". This is not entirely helpful because when someone looks at their task list they could have multiple "example task 1"'s from multiple projects. Displaying UNIT 1 as the referencing master item means nothing to the user. What I want displayed is the Master Project title so that they can sort their tasks by project. Sorting by "Unit x" means nothing.
Now my initial solution was to create a "project" column on the task list. In this column, I could create another subworkflow that all it would do would be to look up the initially created project by looking up and referencing workflow and item id's and set this new "project" variable to the initiating master project (project a - for this example). That workflow WORKS!
However, and this seems to be an issue that is "not uncommon"in MOSS 2007, having this subworkflow running on the task list can (and has) created multiple lock errors which show - "this item cannot be modified as it is locked by an already running workflow". This error grinds the workflow to a halt and is not an error that is recoverable. I have researched this error and it is an unavoidable error that has no single and easily deployable solution. It has something to do with the backend databasing and how/when it stores the update task item variables and so on. Once the workflow locks, you're done.
So, what I really need is a clever solution to associate the main project with any and all subtasks. If the task is created by the "project start" workflow, that is done automatically because the "link" column auto-associates this task with the creating item...which in this case is "project a" - easy enough. However, because of my NEED for the additional subitems on a separate list with their own workflows.....I lose that reference.
Is there a way to associate the tasks created from the subproject list workflows to the main project without having to call another subworkflow to set that variable. (ie: a way to avoid the "this item is locked by a running workflow" problem).
I think I am thinking too hard on this solution and can no longer see the forest for the trees.
Unfortunately I think your solution is to stop using SharePoint Designer for this workflow. Either look into purchasing a 3rd-party workflow product for SP2007 or build a workflow feature in code using Visual Studio.
You want to get to a position where 1 workflow can do everything you're talking about: run on a project and create 4 parallel branches, each which create tasks exactly how you'd like (with a Project column) rather than the very limited options you have from SPD.