Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Create a project

Log in to subscribe to topics and get notified when content changes.

Create a project

Define important aspects of the project such as duration, estimated cost, and the net value to the organization.

Before you begin

Role required: it_project_manager
Note: In previous releases, the it_project_manager role was named project_manager.

About this task

You can create a project from the Projects list or project planning console.

Note: You can also create a project from project workbench or demand workbench.


  1. Create a project.
    From the Projects list Navigate to Project > Projects > Create New.
    From the planning console
    1. Navigate to Project > Projects > Planning Console.
    2. Click the down arrow next to Planning Console.
    3. Select Create New Project. The Project form overlays the console.
  2. Fill out the Project form.
    Note: The fields shown below are shown when the Project Portfolio Suite is active and the Project form is in the Basic view. You might need to configure the form to see these fields.
    Table 1. Project form fields
    Field Description
    Project Name [Required] The name of the project.
    Project manager The project manager assigned to this project.
    Portfolio The primary portfolio to which this project belongs. A project can belong to multiple portfolios.
    • If a project, for which the Portfolio field is not set, is associated to a portfolio using the portfolio form, then the portfolio name gets populated in the Portfolio field.
    • If a portfolio is deleted, the portfolio name is removed from the Portfolio field on the Project form.
    Program The program to which the project belongs.
    Note: If the Portfolio field is not set, you can select from the list of all programs in the system. If the Portfolio field is set, you cannot select those programs that belong to the other portfolios.
    Goal Enter the project goal. You can select only one goal. The goal is derived from the portfolio.
    Configuration item The configuration item (CI) affected by this project.
    Number A system generated number with a configurable prefix.
    State The current state of the project. All new projects begin as Pending and automatically change to Work in progress when you click the Start project button on the Project form.

    Following are the default states: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, Closed Skipped.

    You can also create a custom state, for each state type. You need to override the state dictionary attributes to add the custom state.

    The following example, explains the behaviour.

    For project tasks, you have created a custom state called Testing for the Work in Progress state type. When you update the project task state to Testing, the project state is also updated to Testing. However, if you have not created a Testing state for the project's Work in Progressstate type, the project state is updated to the default Work in Progress state.

    Percent complete The percentage of the project that has been completed.
    Calculation The type of calculation to use for task dependencies:
    • Manual: task dates do not reflect any changes made to dependencies.
    • Automatic: task dates are automatically updated to reflect any changes made to dependents or child tasks.
    Description A detailed description of the project.
    Date tab
    Schedule The work schedule to be used for this project:
    • The default schedule is an 8-hour work day (from 8 to 12 and 1 to 5). A day is considered as a working day, not a 24-hour day.
    Planned start date The intended date the project should begin. This value is set to the earliest time that the project schedule allows. For example, if the project task is created at 3 P.M. and the default schedule is in use (which has an 8 A.M. start date), the default task start is 8 A.M. the next day. Note: The planned start date must be within 15 years of the current date.

    Click the calendar icon and select a date to start this project. Projects do not automatically start on the planned start date. The project actually starts when you click Start project on the Project form.

    Planned end date The intended date the project should end. After you add tasks, this field is calculated from the tasks.
    Planned duration The expected duration of this project. After you add tasks, this field is calculated from the duration of the tasks. The duration also considers the project schedule, accounting for any non-work time in the schedule. For example, if the default schedule is used, with a standard 8-hour work day, a project that starts at 8 A.M. on July 1 and ends at noon on July 2 is calculated as 1 day and 4 hours, not 28 hours. Any project or project task with no children is restricted to a maximum duration of 1500 days.
    Planned effort An estimate of how much time this project will take to complete. This is a rolled up calculation that sums planned effort values for all tasks in this project. After you add tasks, this field becomes a read-only roll up calculation and overwrites any earlier entry that you made.
    Actual start date The date that this project actually began.
    Actual end date The date that this project actually ended.
    Actual duration The actual duration of the project from project start to project closure. As with planned duration, the actual duration shows total project time and takes the project schedule into consideration.
    Actual effort The actual number of hours charged to the resources on this project. If you are using the Time Cards application, the application automatically calculates the value for this field using the totals for the time worked from the time cards of all the resources who worked on this project.
    Financials tab
    Estimated cost An estimate of the cost of this project.

    This value is rolled up from the cost breakdown of the project.

    If there are no cost plans, the estimated costs of the project tasks are rolled up in this field.

    You can also enter the value manually. Select a currency icon and enter a value.

    Actual cost The actual cost of this project. Select a currency icon and enter a value.
    Budget cost Budgeted cost for this project. This field is automatically populated from the project budget breakdowns in cost plan breakdown table. When project funds are allocated for a fiscal year, the cost plan breakdown stores the budget allocation for each fiscal period. These amounts are rolled up and stored in the budget cost.

    Select a currency icon and enter a value if you want to manually enter a value.

    Planned benefit Enter the planned benefit for the project.
    Planned return Planned returns value is derived from the difference of the Planned benefit and Estimated cost values.

    (Planned benefit - Estimated cost)

    Planned ROI% The result is calculated based on values in the Planned return and Estimated cost fields.

    (Planned return/Estimated cost x 100)

    Note: If the cost values are rolled up from the cost plans, the currency in which the roll up happens is determined by the currency property com.glide.financial_management.currency_code. If the property is not set, then the currency is derived from the global currency of the instance.
    Notes tab
    Watch list Allows users to subscribe to project notifications.
    Work notes list The list of users to receive email notifications when the work notes on the project are updated.
    Activity / Work notes Information about the milestones, impediments, or changes as the project progresses. Enter the notes in the Activity field and click the Work notes button. The text appears in the feed below.
    Resource Cost tab
    Planned Cost Planned costs from the Resource plans associated to the project and project tasks.
    Allocated Cost Allocated costs from the Resource plans associated to the project and project tasks.
    Related Links
    Planning Console Opens the Project Planning console.
    Project Workbench Opens the Project workbench.
    Manage Stories Opens the Manage Stories console.
    Create Baseline Creates a new baseline.
    View Story Points by Sprints Displays story points by sprints.
    Related Lists
    Project Tasks The tasks in the current project. Only the next-level tasks (immediate subtasks) appear in this related list.
    Sub Projects The child project records of the current project.
    Resource Plan Lists the resource plans of the project and project tasks. Click New to create a new resource plan.
    Baselines A collection of all planned dates for all tasks and milestones at the time you create the baseline.
    Stories The list of stories in the current project.
    Time Cards Lists the time cards submitted against the project. Click New to create a new time card.
    Requirements Lists the project requirements with their status.

    Click New to create a new requirement.

    Click Edit to add existing requirement to the project.
    Risks Lists the risks that are part of the project.

    Click New to create a new risk.

    Project risks are added with the program and the primary portfolio.

    Issues Lists the issues included in the programs.

    Click New to create a new issue.

    Project issues are added with the program and the primary portfolio.

    Status Reports Lists the status reports from the project.

    Click New to generate a new status report. See, Create a project status report.

    Cost Plans

    Lists the cost plans included in the project.

    Click New to create a new cost plan.

    Cost Breakdown Lists the project level cost breakdowns for each expense type with fiscal periods.
    Project Budget Lists the project budget by fiscal year. Project budgets are created at the portfolio level and also appear in the Planning & Budgeting related list on the Portfolio form.
    Expense Lines Lists the project's expense lines.

    Click New to create a new expense line. See, Create an expense line.

  3. Click Submit.