You are here : How To Use SigmaPro»Create Projects
Creating New Projects
 

There are two ways to add projects to SigmaPro.  You can upload a SigmaPro Project file (these files have a file extension of OPJ) that you have downloaded from SigmaPro in the past or from OnyakTech.com, or you can use the New Project Wizard.  To upload a SigmaPro Project File, click on Projects from the module menu, the Full Main Menu of SigmaPro or from the main Toolbar in SigmaPro if you have it displayed.  At the bottom of the module you will see a Browse button, click this button to locate the SigmaPro Project file you want to upload and then click the link to Upload Project. 

When you upload a SigmaPro Project file, SigmaPro will try to match each Owner, Assigned and Requester of every item in the project to a user in your DotNetNuke web site.  If the user is found, then a match is made and the item will be created as it was originally.  If a user is not found, the current users profile is used.

 

To create new projects in SigmaPro...

  1. Open the Project List by clicking on “Edit Projects” in the modules Edit menu or clicking Projects icon in the SigmaPro toolbar or from the Main Menu of SigmaPro.
  2. Once the Project List opens up, click the “Create New Project” button. This will start the New Project Setup Wizard.
  3. The New Project Setup Wizard will walk you through the steps to create a new project in SigmaPro.  There are ten steps in this wizard.  You can change any aspect of your project after it has been completed, the Wizard is there just to simplify the setup of new projects.
  4. Step 1: Project Description
    • Enter a name and description for the project.
    • Enter the name of the product manager for this project (a project manager must be a member of either the Administrator or Project Manager Role).
    In this context, the Administrator is an administrator of the DNN Portal. The Project Manager Role is specified in the Advanced Security Options of SigmaPro. When Advanced Security is enabled, Project Managers can only create and view issues/tasks. They can not edit the issues. When Advanced Security is disabled, Project Managers can view and edit all issues regardless of the relationship of the issue to the project manager.
  5. Step 2: Project Categories
    When you create an issue, you assign the issue a category. You can create unlimited sub-categories for your project to organize your issues. When you setup your categories, keep in mind the types of reporting you will want to execute on your project in the future.
    • Add categories by typing the name of the new category into the text box and then clicking the Add button.
    • You can add subcategories by selecting a parent category from the dropdown list and then following step 1.
    For CRM projects, Categories may be Meetings, Contracts, Sales Leads, Opportunities, etc.
    For Software projects, Categories may be Bugs, Reporting, Installation, Framework, etc.
    For Support Desk projects, Categories may be Network, Printer, Software, etc.
  6. Step 3: Project Status Codes
    When you create an issue, you assign the issue a status such as In Progress or Completed.  Optionally, you can associate each status code with an image.  If you don’t want to use images for the status codes, just type the name of the status and click “Add Status” while keeping the default “none” selected.
    You can remove status codes by clicking the “Delete” button for the code.
    The text for each Status will appear in the status codes list in each issue and in the text for the image displayed in the Issue List (if you use an image, the text will appear when you hover your mouse over the image). If you don’t specify an image, the text will be displayed in the Issue list.
    Status Codes in SigmaPro can have an associated Status Type. Status Types help automate specific tasks in SigmaPro. For example, by assigning a Status Code a Type of “Minor Software Release”, all tasks with this status will automatically appear in the Software Releases view of SigmaPro.  When you click "Mark Complete" in the issue detail screen, the Status Code of type Closed is assigned to the issue.
    Available Status Types:
    • Minor Software Release
    • Major Software Release
    • New Item
    • Closed
    • Known Error
    • Normal
    • Critical Incident
  7. Step 4 and 5: Project Priorities and Milestones are setup the same as Status Codes (with the exception of Status Types) and follow the same rules.
  8. Step 6: Custom Fields
    You can add one or more custom fields to a project by assigning a data type and typing the name of the custom field in the text box provided. In addition, each custom field can be marked as either required or optional.  Custom Fields are displayed in the core SigmaPro module and in the Help Desk module. These allow you to collect additional information that is specific to your organization.
    You can select from the following data types for your custom fields:
    • String
    • Integer
    • Double
    • Date
    • Currency
  9. Step 7: Phases  Phases are optional.  Phases are displayed in the main task list of a project and provide a means to easily provide information about the current status of each project.  For example, in a Software Development project you may setup phases to indicate the development phase of the project (Alpha, Beta, Delta, etc).  In a project setup to list job openings, you may use this to indicate if your company is hiring or not.  You can prevent the current phase from appearing at the top of the task list from the module menu option Edit SigmaPro-->User Interactions.
  10. Step 8: Project Teams:  In this step, you assign Teams to your new project by selecting a team in the list of available teams on the left and clicking the arrow to move the team selected into your new project. 
  11. Step 9: Custom Forms: In this step, you assign a custom form you have created in SigmaPro to your project.  Custom Forms are created from the Forms Manager listed in the Full Main Menu of SigmaPro.  With this release, SigmaPro uses an old version of the H2O Form rendering engine.  This will change in the next release to use the current H2O Forms engine.  Custom Forms can be used to create more complex data collection forms in place of using Custom Fields.  Another option is to use the current version of H2O as your front end to SigmaPro and use the H2O Scripting functions to post new information directly into SigmaPro.
  12. Step 10: Project Created  There is nothing to do on this step, it is just to inform you that your project has been created and is now ready for use.

 

Customize the SigmaPro Images
You can create your own images to represent Status, Priority and Milestone codes. These images are stored in DesktopModules\Onyak Sigma-Pro\Images from the root directory of your DNN installation. To add available images, simply copy the images into that directory and SigmaPro will instantly make them available for use. These images are 16x16 and have a dpi of 96.

73 Additional Images
SigmaPro includes 73 additional images in the DesktopModule\Onyak Sigma-Pro\Images folder of DotNetNuke. None of the images in that directly are directly used by SigmaPro. To make them available for use, simply copy them into the folder you wish to make them available for (Milestone, Priority and Status). The ModEditor folder is not of use for this function.

 


Copyright 2011 by OnyakTech LLC - www.OnyakTech.com
Privacy StatementTerms Of Use