collabnet sourceforge enterprise 5.0 eval guide€¦ · sections may refer to artifacts created in...

of 45

CollabNet SourceForge Enterprise 5.1 Evaluator’s Guide Thank you for evaluating CollabNet SourceForge Enterprise 5.1. This Evaluator’s Guide will help you experience the major features of CollabNet SourceForge Enterprise (CSFE) by walking you through some common usage scenarios based on sample projects and users already present in your VMware download. If you have any questions or comments about this guide, or installing and configuring the trial, please feel free to post in our feedback forum. Required Setup This guide assumes you have already downloaded and installed the CSFE VMware trial. Visit http://www.collab.net/products/sfee/getit.html to download the trial software. Refer to the CSFE on VMWare Getting Started Guide for instructions about how to install and configure the trial download. Each of the sections below assumes you have completed the previous sections. Later sections may refer to artifacts created in earlier sections, and also provide less detailed instructions for common steps, such as logging in and navigating within CSFE. Sample Users To simplify the evaluation, this guide only uses four users:

• The default site administrator (User Name: admin, Password: admin) • A development manager (User Name: Dev_Mgr, Password: admin) • A developer (User Name: Developer, Password: admin) • A QA engineer (User Name: QA, Password: admin)

In the following examples, the development manager user also performs all the duties normally associated with a project manager. Once you have completed the exercises in this guide, feel free to delete all of the sample users (see the Clean-up section at the end of this guide for details) Contents Initial Set-up: Configuring E-mail Addresses for the Sample Users.................................. 2 Section 1: Feature Request Triage ...................................................................................... 4 Section 2: Requirements Document Review .................................................................... 10 Section 3: Bug Triage ....................................................................................................... 13 Section 4: Context-based Development in Eclipse........................................................... 16 Section 5: Setting up Projects and Roles .......................................................................... 26 Section 6: Configuring workflows.................................................................................... 34 Section 7: Managing Project Content ............................................................................... 41 Clean-up: Deleting the Sample Users ............................................................................... 45

http://www.collab.net/sfeesupporthttp://www.collab.net/products/sfee/getit.htmlhttp://help.collab.net/topic/csfevm510/tasks/installcsfevm.html

of 45

Initial Set-up: Configuring Email Addresses for the Sample Users Log into CSFE as the site admin user: • User Name: admin • Password: admin

Click the Admin tab at the top of the page.

Under Site Administration, click the Users icon.

Click the Nathan Fillion link (Nathan is the development manager sample user.)

Click the Edit button.

of 45

Replace the email address [email protected] with the email address you want to associate with the development manager user. Notifications to the development manager are sent to this email account, and messages sent to CSFE from this account are identified as coming from the development manager user. Click the Update button.

Return to the User Admin page by pressing the Back button on your browser three times. Click the Gina Torres link (Gina is the developer sample user.) Click Edit and replace [email protected] with the email address you want to associate with the developer. Make sure this is a different address than the one you entered for the development manager user. Click the Update button. Click ‘LOGOUT’ at the upper right of the page to log out as the site admin user.

Return to the User Admin page by pressing the Back button on your browser three times. Click the Jewel Staite link (Jewel is the developer sample user.) Click Edit and replace [email protected] with the email address you want to associate with the QA engineer. Make sure this is a different address than the one you entered for the developer and development manager users. Click the Update button. Click ‘LOGOUT’ at the upper right of the page to log out as the site admin user.

of 45

Section 1: Feature Request Triage In this section, you will learn how CollabNet SourceForge Enterprise can help development organizations triage incoming feature requests by enabling users to:

• Globally search for related assets and duplicate issues • Weigh new requests against existing issues • Link relevant discussions to provide context and traceability • Assign issues and tasks to team members so requests can be tracked to

completion View a short video demonstrating these steps (select the first demo in the list, entitled “1. Feature Request Triage”) Part 1: Respond to a request on the Brokerage System forum

1a. Log into CSFE as the development manager user: • User Name: Dev_Mgr • Password: admin

1b. Under My Workspace, click the Monitoring icon.

1c. Click the Enhancement Discussions link. The Enhancement Discussions forum is one of the objects being monitored by the development manager. By monitoring a forum, users can receive email notifications when new posts are made in that forum.

1d. Click the Can we get a single mutual fund order processing screen? link (topic1012).

1e. To reply to the post, click the Reply button in the lower right, and then enter a message like I think I remember a similar request. Let me look into it. When you are done, click the Save button.

Part 2: Perform a global search for existing items related to the new

http://www.collab.net/products/sfee/demo/

of 45

request 2a. Click the Search tab at the top of the page.

2b. In the Keywords box, enter this text: multiple step order. Do not use quotes. When you use quotes, Search looks only for the exact phrase. If you don’t use quotes, Search looks for any of the words (giving a higher search score for items that include more of the words). Other search options, such as wildcards and fuzzy searches, are discussed in Section 2 of this guide. In the In box, select all of the tools by clicking Discussions, and then holding down the Shift key and clicking Wiki. In the In Projects box, select All Projects. Click the Search button in the lower right to start the search.

2c. The search returns results from a number of different tools – click Discussions and Documents in the left panel to view these results. Note that CSFE can index and search hundreds of different file types, including Microsoft Office files, Adobe PDF files, and even AutoCAD files. Click Tracker in the left panel to view the issues (referred to more generically as artifacts in CSFE) that were returned by the search. Note that the search found artifacts across multiple projects. Click the Implement single step process for placing mutual fund orders link (artf1025) to go to the view artifact page.

3: Associate the new forum post with the existing request

of 45

3a. On the view artifact page for artf1025, review the different fields and the values that can be assigned to them in the drop down menus. CSFE makes it easy to customize Tracker fields and workflows to manage feature requests, bugs, requirements, support tickets, and so on. (See Section 6 of this guide to learn more about customizing Tracker fields and workflows) Click the Associations tab.

3b. Associations are bi-directional links that make it easier for users to capture and communicate history, context, and status, while providing managers with better traceability and auditability. Because all of the items in CSFE share a common object model, any item (code commit, issue, document, forum post, file release, wiki page, and so on) can be associated with any other. Click the Add button to add a new association.

3c. In the pop-up window, in the Enter Item ID box, enter post1016. Click the Next button. On the next page, enter a comment like Linking new post regarding this feature request and click the Finish button. Click the Close button to close the pop-up window, then scroll down in the main browser window to view your new association.

4: Evaluate open feature requests 4a. In the breadcrumb at the top of the page, click the Feature Requests link to view the entire list of artifacts in the feature requests tracker.

of 45

4b. Click the Columns icon to open the column configuration menu. Click benefits to apply a previously saved column configuration that includes columns for fields like estimated hours, exec team approval, benefit, budget, and audience.

4c. If you see a Show filter icon in the row of icons above the table, click on it to reveal the filter drop-down menus (if you see a Hide filter icon, the drop-down menus should already be visible)

4d. Click some of the filter drop-down menus to see how users can filter the artifacts list by selecting specific fields and values. Click the Apply filter icon to see how your selections constrain the list of displayed artifacts. Click the Remove filter icon to remove your filter and show the entire list again.

4e. Click the Saved filter icon to open the saved filter menu. Click approved to apply a previously saved filter that only displays artifacts that have an approved value for the exec team approval field. 4e. Update multiple feature requests by selecting the check boxes next to the two Priority 2 artifacts (artf1025 and artf1026), then clicking the Mass Update button in the lower right.

of 45

4f. On the Mass Update page, open the Assigned To drop-down list and select Gina Torres to assign the selected artifacts to our developer user. Open the Priority drop-down list and select 1 – Highest to escalate the priority of the selected artifacts. Click the Update button in the lower right.

5: Create a new task 5a. Click the Tasks icon at the top of the page.

5b. Under Task Summary, click the New Product Introduction link to open the task folder being used to track product release tasks.

Click the Create button in the lower right.

of 45

Enter a Task Name, such as Generate Javadoc for the new mutual fund order screen and a Description, such as We need to document the APIs for the new mutual fund order screen. To assign this task to the developer user, change the fields to: • Priority: 3 - Medium • Assigned To: Gina Torres Click the Save button in the lower right.

of 45

Section 2: Requirements Document Review In this section, you will learn how CollabNet SourceForge Enterprise enables teams to use wildcard, Boolean, fuzzy, or exact phrase searches to locate related requirements, then easily manage and participate in document reviews via email. View a short video demonstrating these steps (select the second demo in the list, entitled “2. Requirements Document Review”) Part 1: Perform a global search for the desired requirements document

1a. While still logged in as the development manager user, click the Search tab at the top of the page. Search for the term requirement across all tools and all projects. Note that only 2 documents (plus 1 document folder) show up in the search results. Click the arrow to the left of Search Criteria to change the search.

1b. Change the search keyword to “req*t?” (without the quotes.) If you have difficulty finding what you are looking for, wildcards like this make it easy to expand your search. Click the Search button and note that 12 tracker artifacts and 2 discussions are now also included in the search results. Change the search criteria once more to “functional specification” – this time, include the quotes – and then click the Search button. Using exact phrases (within quotes) helps you limit your search when you get too many results. Also, you can always jump directly to an object by entering its object ID in the ‘Jump to ID’ box in the upper right of every page. Click on the ‘GO’ button next to the box to view some examples. Click the ‘x’ in the upper right of the pop-up to close it.


of 45

1c. Click the Brokerage System Functional Specifications link (doc 1007).

Part 2: Manage the document review

2a. Below the Document Details section, notice the Versions tab. Documents uploaded to CSFE are automatically versioned, making it easy to review or roll back to an earlier version. Click the Review tab to view the document review status.

2b. Click Brokerage System Functional Specifications Review.

2c. Click the Send Reminder Email button.

2d. Type a reminder message, check the Attach Document to Email checkbox, and then click the Send button.

Part 3: Respond to the document review

of 45

3a. Go to the email account you associated with the developer user in the Initial Setup section. Open up the email reminder and review the attached document. Make a few edits to the document, and save it.

3b. Reply to the email reminder, attaching your edited version of the document. Note the email address from which the reminder was sent: docr1001@[YourServerAddress]. Comments and attachments can be appended to many types of CSFE objects (such as Tracker artifacts, document reviews, and discussion posts) by simply sending an email to the object ID. New issues can also be submitted by sending email to the Tracker ID, as shown in Section 3.

3c. While still logged in as the development manager user, return to the Document Review page. Scroll down to see the email response and attachment you sent as the developer user. As there are no more outstanding reviewers, click Close Review to close out the review.

3d. Select Change Status to Final, and then click OK.

3e. Under Review Details, click the Brokerage System Functional Specifications link, and then click on the Edit / Update button on the right.

3f. Check the Lock Document checkbox. You can lock finalized documents (or documents you are actively working on) to prevent others from editing it.

of 45

Section 3: Bug Triage In this section, you will learn how CollabNet SourceForge Enterprise enables users to submit defects via email, auto-assign them to a team member, use global search to find related code commits and issues in another project, set a dependency between the new bug and the existing issue, then prioritize and reassign the issues. View a short video demonstrating these steps (select the fourth demo in the list, entitled “4. Bug Triage”) Part 1: Search for existing issues related to a new defect report

1a. While still logged in as the development manager user, click the Project Home icon.

1b. Scroll down to the bottom of the project home page. In the Tracker Searches component, click the triangle titled Artifacts Assigned to Me. Project page components such as this make it easy to share information with team members and stakeholders. (You can find out more about project pages and components in Section 7) In this Tracker Searches component, click the Ordering gui hanging link (artf1043). Notice that the support engineer reporting the defect indicated that it is likely related to a JDBC connector problem.

1c. Click the Search tab at the top of the page and conduct a search for artifacts related to jdbc across all tools and projects. Note that in addition to Discussions and Trackers, two Source Code Commits appear in the search results. Being able to search for, and associate other objects to, code revisions improves productivity for developers and traceability for managers.


of 45

1d. On the left side of the Search Results section, click Tracker (2). To view the related issue in the Java Application Server project, click artf1037: Oracle jdbc connector. 1e. Scroll down to review the latest status and comments about this defect. Click the various tabs to review the change log and associations for this defect. Note that tracker fields and their associated workflows are fully customizable (see Section 5 for more details).

Part 2: Create a dependency between issues

2a. Click the Dependencies tab. In the Parent section, click the Choose Parent button.

of 45

2b. In the pop-up window, from the Recently Viewed list, select artf1043 : Ordering gui and click the Next button. In the Dependency Comment box, enter a comment like Linking to dependent issue. When you are done, click the Finish button. Click Close to close the pop-up window. 2c. To return to the original defect, scroll down to the Parent section and click the Ordering gui hanging link (artf1043). Change the Status as follows: • Status: In Development • Priority: 1 - Highest • Assigned To: Gina Torres • Reported in Release: Release 4.6 Click the Update and View button to save your changes. 2d. Now try to change the Status field to Closed. Note that the custom workflow rules defined for this defect tracker requires a comment to be entered to change the status of a defect to Closed. Enter a comment and click the Update button. Note the message at the top of the screen indicates that this defect cannot be closed because it has open child artifacts. Click ‘LOGOUT’ at the upper right of the page to log out of CSFE.

of 45

Section 4: Context-based Development in Eclipse

In this section, you will learn how to:

• Set up the CollabNet Desktop - Eclipse Edition for use with CollabNet SourceForge Enterprise, check out code, modify it, commit changes to the branch, and merge those changes from the branch to the trunk

• View CollabNet SourceForge Enterprise artifacts from within Eclipse, associate your code changes to an artifact during the commit process, and then change the issue status to Ready for Test according to predefined workflow rules.

• Use CollabNet Desktop - Eclipse Edition to automatically save and restore opened files, SourceForge issues, and other context when switching from one task to another.

Before beginning this section, first install the CollabNet Desktop - Eclipse Edition. Detailed instructions are provided here: http://www.collab.net/products/desktops/getit.html View a short video demonstrating these steps (select the fifth demo in the list, entitled “5. Context-based Development in Eclipse”) Part 1: Open the CollabNet perspective

1a. Click Window->Open Perspective->Other

http://www.collab.net/products/desktops/getit.htmlhttp://www.collab.net/products/sfee/demo/

of 45

1b. Select CollabNet; then click the OK button.

Part 2: Create a new CollabNet site 2a. Open the CollabNet sites view by going to Window-> Show view->Other; then selecting CollabNet Sites.

2b. In the CollabNet Sites window, click Add CollabNet Site.

of 45

2c. Enter the URL of the CSFE Subversion repository for the Brokerage System Project. Note that it will have the form: http://yoursourceforgeurl/svn/repos/brokerage_system Enter these values: • Description: Brokerage System Sample

Source Code • Type: CollabNet Subversion

Repository. When you’re done, click the Finish button.

2d. A dialog box appears asking for your name and password. Enter these values: • Username: Developer • Password: admin To save the login information across sessions, check the Save Password checkbox. Part 3: Check out source code 3a. Expand the folders by clicking the + sign next to the site you just created. Browse to the branches/Maint4.6 folder.

3b. Right-click the Maint4.6 folder and select Checkout. Choose Check out as a project in the workspace. Keep the default Maint4.6 project name and the other default options and click the Next button. Choose a directory to use as your workspace directory, and then click the Finish button.

of 45

3c. Go back the Brokerage System SampSource Code and browse to the trunk foldRight-click and select Chec

le er.

kout and choose heck out as a project in the workspace.

t

ctory, and then the click inish button.

C Keep the default trunk project name and the other default options and click the Nexbutton. Choose a directory to use as yourworkspace direF

Part 4: Create a task repository 4a. In the Task Repositories window, click Add Task Repository.

4b. Choose CollabNet – SFEE Tracker and click Next.

of 45

4c. Enter this information: • Server: • Label: Demo image trackers • User ID: Developer • Password: admin You can save the password so that you do not have to re-enter it at the start of each session. Click Validate Settings to make sure you have entered the correct data and Eclipse can authenticate you as a user. Then click the Finish button.

Part 5: Create queries 5a. Once you have created the task

ppears asking you uery. Click the Yes

repository, a dialog box aif you’d like to add a qbutton to continue.

5b. Enter this information: • Query Title: Defects Assigned to Me • Project: Brokerage System (Sample) • Tracker: Defects • Assigned to: Gina Torres When you are done, click the Finish button.

5c. You now see this query and the results in the Task List window.

of 45

5d. You create an additional query, right-click the Demo image tracker task repository and select New Query.

5e. Enter this information: • Query Title: My Feature Requests • Project: Brokerage System (Sample)

Tracker: Feature Requests

the Finish button. • Assigned to: Gina Torres When you are done, click

5f. You now see this query and its results in the Task List, underneath the first Defects query you previously created.

Part 6: Activate an artifact and begin working on code

of 45

6a. In the Task List window, under My

p mut ivate.

Feature Requests, right-click artf1025: Im lement a single step process for placing

ual fund orders. Choose Act

6b. Go to the Navigator window to choose the files to work on. Note: By default, Eclipse sets the Navigator window to Focus on Open Tasks. This

asks toggle. You then see both branches you have previously checked out.

means only files that are in the context of the active task are displayed. To show all files, click the Focus on Open T

6c. Navigate to Maint4.6/src/CastorReadXMLTest.java and double-click to open the file in an editor. Make some code changes and save them.

Part 7: Switch to a high priority defect and work on code.

of 45

7a. In the Task List window, under DefecAssigned to Me, right-click artf1023: Oof memory error. Select Activate.

ts ut

Navigate to Maint4.6/src/FunctionalityTest.java, double-click on the file to open it in an editor, make some changes to the file, and save them.

Part 8: Commit code changes for the high priority defect to the maintenance branch

8a. In the Navigator window, navigate to the Maint4.6/src folder, right-click, and select Team->Commit.

8b. A Commit comment box appears. Notice that the artifact status, id, and title,as well as the URL for the artifact, are pre

-

populated into the Comment box. You can modify the existing text or add additional text before committing the changes. After you enter the comment, click the OK button. Note: the artifact id must be contained within square brackets [ ] within the

ls to comment to associate the commit detaithe artifact the code changes are for.

Part 9: Merge changes from the 4.6 Maintenance branch to the trunk

of 45

9a. In the Navigator window, select the trunk folder, right-click and select Team-> Merge.

9b. The CollabNet Desktop merge tool

, wizard appears. Choose Change set mergeand then click the Next button.

9c. Enter this information: • Merge From -

nt4.6

it associated with artf1023. Choose

sion

a ht-

click the trunk folder and select Team->Commit to commit the changes to the trunk. To complete the check in, enter comments and click the OK.

/svn/repos/Brokerage_System/Mai(the repository URL is pre-populated for you, so you can leave the default setting.)

• Artifacts: artf1023 When you are done, click the Next button. On the next screen, you see the comm

vision rethe revision and click the Finish button.Since on conflicts occur, the newer verof the FunctionalityTest.java file will be updated into the trunk working copy. Notice that trunk/src/FunctionalityTest.javnow shows as being a modified file. Rig

Part 10: Update the artifact details

of 45

10a. To view the artifact details from wiEclipse, in the Task List window, under Defects

thin

Assigned to me, double-click artf1023: Out of memory error. To expand the section, click the Attributes. Then change the status to Code Complete.

10b. Scroll to the bottom of the artifact,

mit enter a comment, and then click the Subbutton.

Part 11. Reactivate the feature

q ete work on it.

re uest to compl11aFeaImp

utual fund orders. Activate.

. In the Task List window, under My ture Requests, right-click artf1025: lement single step process for placing

m Select

11b. You see that the Maint4.6/src/CastorReadXMLTest.java fthat you previously worked on is now

ile

opened in an editor. You can now recontinue working on the code changes for this feature and then commit them.

of 45

Section 5: Setting up Projects and Roles

ollabNet SourceForge Enterprise makes it easy to ess templates and assign role-based access to tools and

In this section, you will learn how Ccreate new projects using procassets.

View a short video demonstrating these steps (select the eighth demo in the list, entitled “8. Setup Projects and Roles”) Part 1: Explore the Agile and Baseline Project Structure samples

1a. Log into CSFE as the site admin user:

• User Name: admin •

Password: admin Click the Admin tab. Under All Projects, click the Agile Project Structure (Sample) link.

1b. On the left side of the page, click Backlog, Work Products, and Key Metrics to review the content on each of these pages, including the portlet-like project components allow you to display data or reports from other tools directly on the project home page. See Section 7 for more details on project pages and components.

reviewing these When you are finishedpages, click Backlog to return to the product backlog page.

of 45

1c. In the User Story Searches component, click the arrow to the left of

r right of this component.

User stories in backlog. Since this is just a skeleton project, there are no artifacts to show. Click the View All button in the lowe

1d. Click the arrow to the left of Shared Tracker Searches. Saved tracker searches can be easily shared with other users by project page com nder the

e”

alue is “User running search.” This allows you to create and share queries that will be relevant both you and to other users.

embedding them inponents. Notice that u

Criteria Summary column for the“Active user stories assigned to msearch, the Assigned To v

1e. Click the Admin tab. Under All Projects, click the Baseline Project Structure (Sample) link. Click the arrow to the right of Lifecycle to expand the

ages sub-pages. Notice how the nested project pages reflect the different stof the development lifecycle. Team members can use these pages to get information on, or track and perform activities within, each of these stages. Click on each of these sub-pages to review their content.

of 45

1f. After you are finished reviewlifecycle pages, click Definition, then in the Requirements Searches component, click on the arrow to the left of Requirements in Definition Assigned toMe. Click the View All button in t

ing the

he

lower right of this component. Click the arrow to the left of Shared Tracker Searches to review all of the saved searches in this project.

1g. Click the Project Admin icon at thtop right of the page. Under Project

e

ields

Admin Menu, click Tracker Settings.Click Defects to review the tracker fdefined for the Defects Tracker.

Part 2: Create a project template 2a. Click the Project Admin icon at thetop right of the page to return to the Project Settings section. Click the Create Project Templa

te button.

of 45

2b. Select Create New Template, then enter a Template Name like Baseline Template and a Description like Template based on Baseline ProStructure. Under Project-Level, check Project Pages. Under Optional Content,

ject

check Shared saved searches (Tracker definitions and workflows are automatically included in project templates). Click the OK button.

Part 3: Create a new project from a project template

3a. Mouse-over the Projects tab at the top of the page, then select Create New Project.

3b.For Project Name, enter Real-time Quotes App. For Description, enter Real-time stock quote application to be

er right.

integrated with the Brokerage System. For Project Template, select Baseline Template from the drop-down menu. Click the Create button in the low

3c. You will automatically be re-directed to the new Real-time Quotes App project. Review the various project pages, components, Tracker fields, and shared Tracker searches to confirm that they are the same as those of the original Baseline Project Structure.

Part 4: Add users and roles to the project

of 45

4a. Click the Project Admin icon at thetop of the page. Under Project AdminMenu, click User Membership. Click the A

dd button in the lower right.

4b. In the Name (search) field, enter Dev_Mgr, then click the Find button. Select Nathan Fillion and click the Next button. Check Founder Project Administrator, then click the Finish button. 4c. Log out as the site admin user, then log into CSFE as the development manager user:

• User Name: Dev_Mgr • Password: admin

Mouse-over the Projects tab at the top of the page, select My Projects, then select Real-time Quotes App. Click Project Admin, then click

u. Permissions under Project Admin MenClick the Create button in the lower right.

4d. For Role Name, enter QA. For Description, enter QA Role. Click the

l

lick on each of the links on the left to r

ol.

ch as , to

l ermissions.

Create button in the lower right. Scroldown to the Role Permissions section.Cview the role permissions available foeach to

For each tool, check all of the check boxes with descriptions in bold, suAll Project Pages and All Trackersassign create, edit, and view permissionsto the QA role. Click the Save button in the lower right once, after you have finished assigning all the toop

of 45

4e. Click the Create button in the lower right to create a second role. For Role Name, enter Development Manager. For

escription, enter Development

in the lower right. Scroll down to the Role Permissions section. This time, when you click on each of the links on

DManager Role. Click the Create button

the left, check the first box in the Permissions section to grant admin permissions for all of the tools to this role. Click the Save button in the lower right when you are finished assigningpermissions.

4f. Click User Membership under Project Admin Menu, then click the Addbutton in the lower right.

4g. the Name (s eld, enter QA, In earch) fithen click the Find button. Select Jewel Staite and click the Next button.

4h. Check QA, then click the Finbutton in the lower right.

ish

4i. Click Permissions under Project

Click the Save button.

Admin Menu, then click the User-Role Matrix tab to review the different users in this project, and the roles that have been assigned to them. In the row for Nathan Fillion, check the box in the Development Manager column to assign the Development Manager role to Nathan Fillion.

Part 5: Add a Subversion repository to the project

of 45

5a. Click the Source Code icon on the top of the page, then click the Create Repository button in the lower right.

5b. For Server, select Subversion from the drop-down menu. For Directory Name, enter rtq, for Repository Namenter real-time-quotes, for Descriptionenter SVN repository for real time quotesapp” Check Association Required on Commit to require developers to includan artifact ID

e, ,

e

Note that permission to access each repository in a project can be

Click the Save button in the lower right.

in the comments field when they check changes into this repository.

individually granted to user roles, such as those you defined in steps 4d and 4e.

5c. Select the radio button to the left of

of the creen. Click on Monitor Selected.

Monitoring a Subversion or CVS repository allows you to receive e-mail messages with the details of every commit to that repository.

real-time-quotes, then click on the Monitor button at the bottoms

5d. Note the checkout command indicated in the right-most column. Enter this information into any Subversion client (for example, TortoiseSVN) to access the source code repository for this project. Note: if you would like to see the detailof the SCM monitoring e-mail, you should sign in as the QA user when you use your Subversion client (monito-mail are not se

s

ring nt to the same user who e

made the change)

of 45

5d. Using your Subversion client, checkout the /svn/repos/rtq directory, then add a file and try to commit it without a comment. Notice that your commit is rejected because associations are required. Try again, this time

e

,

entering [artf1043] (including the squarbrackets) in the comment field. If you made this commit as the QA useryou should receive an e-mail notification at the e-mail address you entered for the Development Manager user.

of 45

Section 6: Configuring workflows

to easily customize the fields and allowed transitions nterprise trackers to enforce governance rules or

e steps

In this section, you will learn howfor various CollabNet SourceForge Estandardize processes.

View a short video demonstrating thes (select the ninth demo in the list, entitled “9.

Configure Workflows”) Part 1: Clone an Existing Feature Requests Tracker 1a. Log into CSFE as the development

anager user: • User Name: Dev_Mgr • Password: admin

m

1b. Mouse-over the Projects tab at the top of the page, select My Projects, then select Real-time Quotes App

1c. Click the Project Admin icon at the top of the page.

1d. Under Project Admin Menu, click Tracker Settings.

of 45

1e. Click the Clone button, then select Clone External Tracker from the drop-down menu.

1f. For the Source Tracker ID, enter tracker1008. This is the tracker id for the

ker.

Brokerage System Feature Requests trac Click the Next button.

1g. For the Title, enter Feature Requests. Enter a description like Feature Requests Tracker for the Real-time Quotes app, then click the Create button.

Part 2: Edit the Cloned Tracker 2a. Under Trackers, click Feature Requests.

2b. Click the Benefit field and, while holding down the mouse button, drag it up above the Executive Team Approval field to reposition it in the artifact layout. Then click the Save Changes button to save the new field ordering.

Part 3: Create a New Defects Tracker 3a. In the bread crumb at the top of the page, click Tracker Settings to go back to the tracker settings page.

of 45

3b. Click the Create button

3c. For the Title, enter Bugs. Add a Description, such as Bug Tracker. Click on

. the Create button to create the tracker

Part 4: Add a New Field to the Bug Tracker

4a. Under Trackers, click on Bugs.

4b. At the bottom of the tracker fields tab, click the Add Field button.

4c. For Field Name, enter Duplicate. For Input Type, select Single Select (Specify Field Values) in the drop-down menu.

4d. In the Values section, click the Add button in the lower right.

4e. Enter the value Duplicate; under ‘Default Value’, select the radio button next to None. Click the ‘Save Field’ button.

of 45

4f. A dialog box will be displayed to confirm that you want to save the changes. Click ‘OK’. Part 5: Verify the Functionality of the New Field 5a. Click the Tracker icon at the top of the page.

5b. Under Tracker Summary, click Bugs.

5c. On the bottom-right of the Bugs section, click the Submit New Artifact button.

5d. Enter a title, such as Test Defect, and a description, such as Testing Duplicate Functionality, then go down to the Duplicate field and select Duplicate from the drop-down menu. Click the Save and View button to save the new artifact and review the artifact details.

of 45

Part 6: Customize the Workflow 6a. Click the Project Admin icon at the top of the page.

6b. Under Project Admin Menu, click Tracker Settings.

6c. Under Trackers, click Bugs.

6d. Click the Workflow tab.

6e. Click Closed to edit the workflow for closed artifacts.

of 45

6f. For the Transition to Status rule “Closed

Status Transition, select “Assigned to” and “Comment” (hold

Click the Save button.

Any”, change the role from “All users with edit permission” to “Developer”. Under Required Fields for

the CTRL key down to select multiple values).

Part 7: Verify the New Workflow Functionality

7a. Click the Tracker icon at the top of the page. Under Tracker Summary, click Bugs.

7b. Click the artifact that you created in step 5d to open the artifact details.

7c. Change the Status to Closed, then click the Update and View button.

7d. Notice that the Status has been updated

atuses for transition. You will notice that there are no other values to choose. That is because you have the Development Manager role and are not allowed to transition a closed defect to any other status. The workflow transitions only allow the Developer role to transition a closed defect to another status.

to Closed. Click the Status dropdown to show available st

of 45

7e. Log out of CSFE and then log in as the developer user:

• User Name: Developer • Password: admin

Mouse-over the Projects tab at the top of thepage, select My Projects, then select Retime Quo

al-

tes App.

7f. Click the Tracker icon at the top of the gs. es,

osed’ link on the right side

the artifact details.

page. Under Tracker Summary, click BuBy default, this page only lists open issuso click the ‘1 Clof the page to view closed bugs. Click the artifact that you created in step 5d to open

7g. Click on the Status dropdown to show available statuses for transition. You will

per to transition an artifact from the Closed status to another one.

notice that you now see the other status values. That is because the workflow has been set up to allow the Develo

7h. Change the status to Open. Notice that the Assigned To and Comment fields are now required. Fill in these values and then click the Update and View button.

of 45

Section 7: Managing Project Content

In t how CollabNet SourceForge Enterprise makes it easy to quickly add and update project web pages, custom issue tracker queries, reports, and

nc and stakeholders informed.

o demonstrating these steps

his section, you will learn

other content to keep team members in sy

View a short vide (select the tenth demo in the list, entitled

“10. Manage Project Content”) Part 1: Experimenting with Project Pages and Components 1a. Log into CSFE as the Development Manager user:

• User Name:

Dev_Mgr

n

• Password: admin Go to the Project Home of the Real Time Quotes App you created in Section 5, thenext to the word ‘Configure:’ in the upper right, click the ‘On’ link.

1b. Experiment with re-arranging the components by clicking on the up and down arrows in the upper right of each component.

1c. Click the Add New Component button above the ‘Project Home’ title

1d. Enter a Title, such as Test HTML Component, then select Text as the Component Type.

1e. Experiment with the HTML editor in the ‘Properties of this component’ section. Hover your mouse over the various tools in the toolbar to see a description of what each of them does. Try entering and formatting some text, inserting a table, and inserting an image. You can upload an image from your computer and it will be available to insert in any project page.

of 45

1f. Click the HTML button in the upper

right of the toolbar to view the raw HTML of your component. Users experienced in web programming can embed javascript and other complex HTML in this Edit HTML Source pop-up. Click the Cancel button to close the pop-up, then click the Save button to save your new HTML component. 1ri

g. Click on the wrench icon in the upper ght corner of your new HTML component.

whether to

in ou want to

stage or test some content before publishing

Here you can change the title of your component, and also choosemake it visible to all users, or hidden andonly available to project administrators con ufig re mode (convenient if y

it widely). Click on the wrench icon again to close thisproperties panel.

1h. Click the Add New Component button t.

aved ches’ button. Select some of

ected’

button. Experiment with re-arranging the Save

again to create another new componenThis time, select Tracker Search Results as the Component Type. Under ‘Properties of this component’, click the ‘Add STracker Searthe saved searches by checking the boxes tothe left, then click the ‘Add Sel

Tracker searches in the list. Click thebutton in the lower right.

1i. Click the arrow next to one of the Tracker searches in your new component to execute the search (unless you have added tracker artifacts to this project, the search will return no results).

1j. Click the Add New Component button again to create another new component. This time, select Project Statistics as the Component Type. Enter a Title, then click the Save button. Try adding and editing some sample tasks and tracker artifacts in this project to see how your new component graphs real-time statistics.

of 45

1k. Click the Edit Structure button on theleft of the page.

1l. Under ‘Edit Content Structure’, click on‘Top Level’. Experiment with re-arranging the pages by clicking on a row in the table to the right and dragging it while holding

own the m

ouse button. When you are dfinished, click the Save Changes button in the lower right.

1m. Experiment with adding new pages andsub-pages by navigating to the desired location under ‘Edit Content Structure’, then clicking the Add New Page button. Click the Project Home icon at the top of the page to return to the main project page.

1n. Click the Document icon at the top of the page. Under the Documents section,

rs. note the existing folders and sub-foldeClick the New icon to create additional folders and sub-folders. Click the Add Document button in the lower right to upload some documents to one of these folders.

of 45

1o. Return to the project home page and click on one of the new pages you created in step 1m.

1p. Click the Add New Component button again to create another new component. This time, select Documents as the Component Type. Enter a title, then scrolldown to the ‘Properties of this component’ section to select the folder you added the documents to.

Next to the word ‘Configure:’ in the upper

r right, click the ‘Off’ link, to navigate through the project pages as an end-usewould.

of 45

Clean-up: Deleting the Sample Users

SFE as the site admin user: • User Name: admin • Password: admin

Log into C

Click the Admin tab at the top of the page.

Under Site Administration, click the Usericon.

s

Check the boxes next to Nathan Fillion, Joss

t Whedon, Gina Torres, Jewel Staite, and Summer Glau then click the Delete button athe bottom of the page.

Click the OK button in the pop-up dialog to confirm.

Now you are ready to create your own users! Don’t forget to visit http://www.collab.net/sfeesupport to join the community forum if you have questions or other feedback – good, bad, or ugly, we love to hear from our users!

Sample Users To simplify the evaluation, this guide only uses four users: The default site administrator (User Name: admin, Password: admin) A development manager (User Name: Dev_Mgr, Password: admin) A developer (User Name: Developer, Password: admin) A QA engineer (User Name: QA, Password: admin) In the following examples, the development manager user also performs all the duties normally associated with a project manager. Once you have completed the exercises in this guide, feel free to delete all of the sample users (see the Clean-up section at the end of this guide for details)