In TFS 2013, in the Backlog view, I change the columns to be displayed, the order and the size, with the "Column options" button. It works fine.
But later, I modify that for all users by editing process file (using witadmin command). Now, all users but me have the same layout.
How can I reset my layout to have the default one too ?
Once you have customized your view, TFS has a record squirreled away in its bowels saying, "Hey, this person has a custom view, ignore the default in the process file."
There is no way via the web interface (or Visual Studio) to get rid of that and default back to the default.
If you have access to the DB backing your TFS installation, you can look through the schema and figure out which records represent the customizations you have made and delete those.
That's about it really.
Related
Is there a way in TFS that user have permission to add Issue in a project and should not have permission to add/edit other work Items like User Story etc ??
is there any extension or utility to do this on TFS ??
You cannot restrict the editing of specific work item types. Permissions are controlled at the area path level. A user with permissions to create work items under an area path can create any type of work item under that area path.
No, there is no such build-in configuration. It's also not able to use any extension or utility to do this on TFS.
Permissions for work items are based on the areas/iterations where they occur, and are set through the dialogue that defines areas and iterations.
In other words, you are not able to set any permission either to a specific work item or work item type.
You could submit a user voice here, our PM will kindly review your suggestion.
There is only one out-of-box way to do this: Create child nodes, modify work items under an area path. You may try the following:
Create new team and area path for Issues Team Add a team, move from one default team to several teams.
Edit Security for the Root Area Path and restrict edit work items for the Issues Team.
Edit Security for the Issues Team Area Path and allow to edit work items for the Issues Team.
In this case, your Issues Team can create and edit any work items under Issues Team Area Path, but can not edit any other work items.
I want to prevent my users from logging work once an issue gets to a particular status. How can I accomplish this?
I have a post-function in my workflow that sets the Resolution, but the "Log Work" item in the More menu still shows up.
I don't see in the Project or System administration any options about it.
You can accomplish this by setting jira.issue.editable to false in the properties of the status in the workflow.
Find the active workflow that applies to the issues you wish change. This is most easily done by either: going to the 'Workflow Schemes' admin page, then clicking on the Workflow link in the row applying to the issues' project and issue type, or clicking View Workflow in the Issue View.
To edit the workflow, you will need to either create a copy of it (if using the default jira system workflow) or edit the draft of the workflow.
In the Workflow Editor, for the 'Closed' step, click View Properties (in Text mode) or Properties (in Diagram mode) to see the step properties.
Editing issues in the selected step is enabled by default, or you will see a jira.issue.editable property with value true. Either create the value or chang the property value to false.
Publish your draft workflow, or if editing a copy, activate the workflow by creating a new workflow scheme associated with the edited workflow, and then associating it with your project.
Reference: https://confluence.atlassian.com/jira/allow-editing-of-closed-issues-138704.html
Does TFS 2013 have the ability to automatically add Templated tasks to a work item?
So I create a work item, it automatically adds some tasks for it such as Code, Test, CodeReview, HelpGuide
Can you guide me to the right place to read about it if it has this ability.
Built-in? Then no.
There is an open source TFS Serverside plugin, called TFS Aggregator which will allow you to run a piece of code every time a workitem changes. Creating subtasks when a parent task changes state or is created is a piece of cake.
See:
https://github.com/tfsaggregator/tfsaggregator/releases
https://github.com/tfsaggregator/tfsaggregator/wiki/Auto-Create-Children
If you don't want to run a server side handler, then you may be able to use a script (powershell can do pretty powerful things when using the Client Object Model).
Or you can use the copy-paste magic of the Excel plugin for TFS. Simply put the tasks you want to create on the clipboard (without an ID) then use the "Insert Rows" paste option to paste them directly under their prospective parent (in a tree based query). Upon publishing the tasks will be associated to the parent. Play with the Title 1, Title 2, Title 3 etc fields to control the nesting.
I have a number of TFS work items where I need to blank out a particular field (the Assigned To picklist). I would like to do this using a template, but if I leave the field empty in the template, it interprets that as meaning I don't want to change that field. Is there any way I can define a template where I tell it that I want to empty this field, when I apply the template to my work items? Maybe some special placeholder like , something like that?
Note: I'm working on TFS work items through Visual Studio 2010; and for some reason the web interface isn't accessible in this project.
Update; for anybody not familiar with work item templates, they are a way to define a batch of changes to make to a work item, which can be applied to one or more items in a single action. This functionality is part of Team Foundation Server Power Tools. Here's an example of a template I use frequently:
Once you have a suitable template defined, you can select a number of work items from a view in TFS, right-click, and apply the template to all of them with just three mouse-clicks in total:
Not sure what you mean by template. But if you have a bunch of work items and you want to do a bulk-update to set Assigned To to blank, I would do that in Excel.
Run a Work Item Query in Visual Studio, click the Open in Office/Excel button, copy-paste blank into the Assigned To field across all the rows, then hit Publish in the Team ribbon tab to publish those changes back to TFS.
I created a custom TFS process template with altered work items. After I uploaded the template to TFS and began testing the new process, I realized I had forgot some state transitions for one of the work items. I altered the XML to include the new transition states and uploaded the process template to TFS again. However, the new transition states are still not showing up in the state drop down list. Is there something else I need to do to refresh the work item or the process template so the new transition states appear in the state drop down list?
You must refresh TFS data from Team Explorer as described here.