I want my base users to have their drop downs for owner/assigned/status/milestone to be defaulted to a certain option like new request/one particular person. Instead of having my users pick through extensive lists of users. Where is the best place to look for / alter this and best method of doing it?

 Thank you

Are you wanting all users within a particular project to be assigned the same default values for that project or are you wanting the default values within the project to be assigned by what role that user is given within the project?  This would be the first thing to determine so that it is known at what level the default values depend, the user or the role.  

Regardless of user role, when someone goes to create a new Issue. The assigned to, owned by, status, milestones, and priorities are all set to a default value.

 So assigned to would be Mr. Jones, owned by Mr Jones, Status = New Issue, Milestone = Startup, Priorities=Normal. etc so the users do not have to select them every time they create a new issue. I don't care if they have the option to change it at creation just want the initial loaded values to be defaulted. We have one person who is in charge of managing all our issues, and we want her as the owned, / assigned to at the start, unless the user picks something different. The other options being defaulted are for convience for users and to provide general guidance for submitting the issues.

I hope that helps explain the issue a bit better. If not please let me know.

And thank you for the help.

I believe I understand what you are asking for, to have one value from the selection drop down list for many of the lists be a default value which populates the field upon entering the web page.

What comes to mind when I think of how to solve this problem is that certain database tables would need to be altered to add a new column which would hold a flag to indicate if that record is to be the default record or not.  For each field you want a default value for, the relating table would have to be altered.  As with any database change the change would need to be worked its way on up the stack of DAL (Data Access Layer) program code from the stored procedures to the data access layer files as well.  The coding for the screens would have to be altered as well for any area you wish a default value set up for to provide the input option to set a certain value as a default value.  The last change that would need to be made would be to the issue input screen itself so that the code that populates the drop down lists for the fields you want default values for will set as the selected value the one field that has the default flag set on it.  Naturally there would have to be some validation checks built into the code when creating the values so that only one of each type can be set as the default value to prevent problems during issue input time.

As with any piece of software I am sure there are other ways to go about resolving the problem but I believe the method I described above would provide the greatest degree of flexibility in the program by keeping the point at which the values are defined as default at the point where the values are created so that as future projects with their own unique values are set up then they can have the appropriate default values set up for them as well.

You have described a need that I had not thought of before when starting to lay out my own issue tracking system so it is something I can keep in mind.  I hope this helps and if you have questions I'll try to answer them.

do like this on issuedetails.aspx.vb in BindOptions() routine