Just starting to implement things on TFS 2010. Been hunting around with no success so have resorted to posting the question.
When we get emails from users detailing a bug, or even suggesting a new feature, how can we create a TFS workitem on their behalf? We'd like to report on where/who the work items are coming from.
Having them create the item is not ideal as many of the users do not have TFS access, and may even be external clients.
The fields that are used for tracking use the credentials of the user that created the work item. If you want to track the customer who created the work item, you need to add a new field where you can store this information.
The CreatedBy field is available for you, but it is - hardcoded - readonly.
Do you know that it is also possible to let your external customers create their own bugs by using "Work Item Only View"? You don't need a CAL for your customer if you use this. In this mode, the customer can create new work items and see their own created work items.
Related
I've allowed my Stakeholders to create Work Items but I would like to restrict them to only be able to create bugs and NOTHING else. Currently they can create ANY Work Item type including Epics... I'm thinking there has to be a way to stop this but I can't seem to find it.
There is no setting for this. And there is already a similar feature request submitted on VSTS User Voice: Hide Work Item Types (WITs) based on permission/security group.
I'm looking to reproduce the Jira watch functionality in TFS 2013. In Jira, you can click a link to watch an item and thereafter you will be notified when anything on that item changes.
I know on TFS you can:
be emailed if anyone changes a bug you are assigned to
manually email a bug to anyone at any time
Create a custom report and pin it to your home page to notify yourself of things (like this maybe?)
I can imagine creating a new field that will accept multiple users and creating a custom email notification to notify everyone in that list if the work item changes. But that seem like a whole lot of work and I'm not sure were to start if that is the way do do this.
What's the easiest way to get functionality like watching a work item? If it's easy and similar to the Jira functionality that is better for me than exactly the same and hard to do.
Sure, you can setup email alerts based on many different criteria, including what you asked for.
You need to go to the Alerts section, and create a new custom alert, and you can put in the ID of whatever work item you want to "watch". By default it includes the clause AuthorizedAs <> [Me] which will make sure it doesn't email you for changes that you make, but you can remove that clause if you'd like.
I am setting up a tfs 2013 environnement,
In a Scrum team project, we would like a few users to be able to create backlog items and tasks, but we would like that other users to only be able to change the task their are assigned. Or at least we would like that these users can modify existing tasks, while not being able to create new one, or move them to other sprints
at this time, with the security parameters i have found, i can only either allow a user to do everything (create and move a backlog items from a sprint to another, modify it, delete it...), or nothing (if you can't create or move, you also can't modify an existing one...)
any clue how i could proceed ?
We have custom work item types and we prevent users from creating certain work items by editing the WIT's xml and including this in the transition between nothing and the "New" state. [global]\TeamSystem-TaskCreation is a TFS security group with a limited set of members.
<TRANSITION from="" to="New" for="[global]\TeamSystem-TaskCreation">
There is no real way to do this I'm afraid. TFS does not have many fined grained access controls, the impression I get is that it is designed to empower people and not restrict them.
You should be able to ask people not to change tasks, if that is your way, and use the Work Item History and/or Alerting functionality to know when they have done something you don't want them to. For example, and task changes not by approved people sends and e-mail to the leads.
We're about to implement TFS 2012 and I've been having some fun customizing some work items to aid us in our reporting. One issue we have is our reporting based on clients.
Our Product Backlog Items keep our requirements, however, we need to report our requirements per client (government regulations). Some requirements will affect all clients, some will only reflect certain ones. I've been able to add a global list of clients along with a multi-select option and that part is working great.
The issue is we need to also note the requirement number for each selected client. I know I can go in and add a field for each 'Client Requirement', but as that list gets bigger, that screen will be insanely huge.
Does anybody know of such a way to implement something of the sort?
One option would be to create a custom Work Item Type for Clients. Then link your PBI's to the appropriate client WI's. When you create a link you can enter a link comment also which you could use to capture the client-specific requirement number.
I would create a custom "Client Requirement" work item that has the list of clients to select and includes a field for Client ID. You can then either use the related link type or create your own, maybe "Implements \ Implemented By" so that you can create a Reporting Services report that pulls the ID's
We're using team system to control our developement (product backlog items, sprint backlog items etc). It's a pretty nice tool but we wanted to allow other users to be able add bugs and new feature suggestions WITHOUT letting them mess with the actual development bits.
I can set these guys up so they add the work items they need but I can't see a way to block access to the bits I don't want them to edit/view. Has anyone else seen this? Has anyone found a solution?
Are you using TFS 2010? If so, you can simply add them to the Work Item View Only Users group. This will grant them access to create new work items and to view/edit any work items they've created (but not others). Check out this link for instructions.