I'm working with TFS 2013 and VS2013 to modify a work item template but there are some issues I cannot resolve.
I want only the person who is assigned to a work item to be able to modify this. Is there any opportunity to set a general rule for this? I already tried to set each field readonly if the authorized user is not equal to the assigned user. But that didn't work for me, I suspect this is because of the difference between display name and system user (domain).
I also want to create a custom action, which automaticly changes the "assignedTo"-User. Unfortunatly I didn't find any proper guide how to define a custom action. Most guides explanes where an action is refered in a transition, but not where it is defined. Do you have any suggestions where to find such kind of guide?
Related
I have an old setup with a tfs2010 and sql2008 and the current Collection is holding 3 team Projects. Now i want to create a new team project but for some reason i cant. it seems that it has something to do with the SQL Reporting that dosent excists. i get an error TF218027.
Ive been going through the setup and im wondering a bit
What exactly does the TFS use the reportServer for (MSDN dosent seem to want to tell me)
is there any way to create a Team project without the reporting
Will it damage my excisting data if i create and connect to a new sql reportServer
Hope someone will take the time to give an answer
thanks.
I have already tried the different approtaches discussed on different threads and im primarily looking for information on the 3 questions written above
Try the steps below:
In browser go to: http://application-tier/Reports/Pages/Folder.aspx
Press Folder settings button in the toolbar
Press New Role Assignment button in the toolbar
Specify user name in Group or user name field, check Content Manager role and press OK.
So for the people that actually read the question the answer is.
Keeps track of agile work progress
yes and its actually easy. go to the reporting service and stop it and then tell TFS not to report under reporting
Since it was never running the answer here is No
Is it possible to customize the "Create Issue" from per role?
In fact, I simply want to show a reduced set of fields for reporters/users to not overwhelm them and prevent incorrect filling out of unnecessary fields.
Developers should see all fields so that they can provide all necessary/internal details.
In JIRA you can install the plugin "Script Runner" which contains a module called "Behaviours". This module allows you to define fields which should be visible for a specific gruoup or not.
In JIRA we don't have ability to customise this without install plug-ins and edit templates on server-side. Maybe most easy way this is create two different screens in issue screen scheme. First screen(simply) for issue create and second screen(full view) for edit&view.
https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/server/overview
Firstly I'm sorry for my english. Ha ha
So, I'm learning to create sites with Ruby on Rails so I started with that framework. I stuck for a few hours because I do not find the right method for something that I try to do.
I try to create a crowdfunding site. I have successfully installed and configured ActiveAdmin and configured it to create projects. I would now like to add a condition into these projects. I would like 4 states: "Empty" when the project is created, but not all features are filled. "Upcoming" when it met all the requirements. And then when it is ready it should get "Upcoming" state. I want my project management panel to be represented on activeadmin. I have a select box that would change the project status to "Validate" or "No validate".
So I thought to simply use the tool 'if condition' to do the above, but my problem is I have no idea of where I should put it. If I put it into the active admin controller, a controller would be created for projects or in my project model? Should I create a method and if so when to call it? Maybe do something else? I struggle to see clearly the whole picture.
Thank you in advance for your suggestions!
We have an existing text field 'Defect Found Version' (DFV) and a new Field I have created 'Defect Found Version Picker'
I have made the Picker mandatory & that works fine, listing all the cersions on the project.
The DFV field is set to 'Optional' on the right hand side of the Configure Field layout page, however next to the name on the left there is the text REQUIRED & I can not see how to disable this.
Even if I remove this field from all screens I get an error when I create a bug saying that DFV is required.
Any thoughts please ?
Look at the Field Configuration Scheme used by the JIRA project. Then look at the field configuration used for that issue type. That's where it is being made required. Unless it's because of the JIRA Behaviour plugin, so check if that is active
Do you have take a look on your Workflow validator ?
Sometimes, it's required on your workflow, and not on your screen.
TFS stores information about who created or who activated a work item and for some reason checks its validity whenever the work item is modified.
When a user is deleted from active directory or renamed in active directory, all work items even slightly has connection with the user can not be modified. Usually the error message is something like ...
TF20015: The field 'Activated By' contains the value 'blah blah blah' that is not in the list of supported values.
I've found a blogpost which recommends tweaking the TFS database, which is something not supported nor recommended by Microsoft.
What can be done to resolve this?
Thanks...
e-mre
Caveat: I'm not sure that this will work, and right now I'm not in a position to test it. However, I've had success with this approach on some other fields.
If you use the TFS Power Tools to edit the work item type definition, you should be able to change the Activated By field's rules and add an ALLOWEXISTINGVALUE rule to it. This might allow you to save those records when the AD name changes.
We've used this with some success with the Assigned To field.
I've seen this behaviour. It occurs if someone who activated a work item is removed from Active Directory (leaves the company) or if they change their name (gets married).
It's simple to fix, you just need to change the work item status from Active to Pending then back to Active this will change the "Activated By" field to the person chaging the status and the problem will be resolved.
Are you using TFS 2008? I seem to remember that this issue is fixed in 2010 (but I might have dreamt that)
If you have a lot of work items this blog might have a solution that helps automate the fix.