Easy!Flow

Q: Can I make my existing SVN repository work with Easy!Flow?
Q: How do I add/delete/rename a field in the ticket UI page?
Q: What's the relationship between a project management task and a development tracking ticket?
Q: How do I backup and restore Easy!Flow?

Q: Can I make my existing SVN repository work with Easy!Flow?

A: Yes. Assume the existing repository is physically located at C:\svnroot\repos_product1, and Easy!Flow is installed at C:\Easy on a server named easyflow_server, here are the steps to set up the proper directory structure for an existing SVN repository:

1. Move "C:\svnroot\repos_product1" to "C:\Easy\SVN_REPOSITORY".

2.
copy C:\Easy\SVN_REPOSITORY\products\hooks\* C:\Easy\SVN_REPOSITORY\repos_product1\hooks\

3. Create a new Easy!Flow product named "product1" for repository "C:\svnroot\repos_product1".

4. Add the new repository to item "repos_url" in "site.conf", the SCMClient config file:

repos_url=http://easyflow_server:1080/svn/products/;
http://easyflow_server:1080/svn/repos_product1/

5. Run SCMClient, select "http://easyflow_server:1080/svn/repos_product1/" as "Repository Root" and check "Create new product" in Login window. Then create an empty product in repository without importing any initial files.

6.
mkdir C:\repos_product1_localcopy
cd /D C:\repos_product1_localcopy
svn co http://easyflow_server:1080/svn/repos_product1
cd repos_product1

If the existing repository "C:\svnroot\repos_product1" already has the standard SVN directory structure:
/trunk
/tags
/branches

svn move trunk/* product1/trunk
svn move branches/* product1/branches
svn move tags/* product1/tags
svn commit -m "move files into the new EasyFlow product"

Otherwise, move all existing directories into product1/trunk:

svn move existing_dir1 existing_dir2 ... product1/trunk
svn commit -m "move files into the new EasyFlow product"

Please refer to this configuration case in chinese.

Q: How do I add/delete/rename a field in the ticket UI page?

A: There are two types of UI fields, system defined and user defined. You need to have administrative privilege to make changes.

For system defined fields:

To add or delete a field: Go to Site Admin->Parameters->System Fields Toggle, then you can check a field on or off.

To rename a field: Go to Site Admin->Parameters->System Fields Rename, then change the field name.

Make sure you click "Save Changes" in the end.

For user defined fields:

Go to Site Admin->Customize Field, then add or rename a field. To delete an existing field, just check the "Is obsolete."

Q: What's the relationship between a project management task and a development tracking ticket?

A: A task (or sub-task) can be associated with none, one or many tracking tickets, depending on the size and nature of a project, and your preference. Of course, it is not worthwhile to show a simple bug fixing ticket as a task. In general, we recommend only new features and major enhancements are recorded as tasks while implementation details are recorded in tickets. So long as the parent-child relationship is properly set among these tickets (e.g., an enhancement is further divided into many work items – tickets – and they are all defined as child tickets of the parent ticket of this enhancement), the system will automatically identify them at the task level. In other words, you only need to associate a task (or sub-task) with a parent ticket, no need to list out all child tickets in the project management level. You right click on a task and select "Assess Task Risk," the system will display all related tickets and their statuses.

Q: How do I backup and restore Easy!Flow?

A: Easy!Flow offers tools to do that. The "backup" and "restore" tools are located at [installation base]/tools (e.g., C:\Easy\tools). For more detail, please refer to "Easy!Flow Backup and Upgrade" document on our Web site under Support->Document.