1) Upgrading from Crystal Gantt (our Standard version)

When you upgrade from Crystal Gantt Standard to our Pro version and a task gets loaded in the Gantt for the very first time, the task values (Start Date, End Date, Sort Order, Progress and Indent Level) are fetched

• From the custom fields, if any, created by you as required by our Standard version.
• If there are no custom fields, then it will check in our database and get the values, if any.
• If data not found in database, then the values will be calculated as mentioned below in #2.

Once calculated, the values will get saved in database and custom fields if configured.

Note: Only when the custom fields are added into appropriate project screens, it will get hold the value.

2) New to Crystal Gantt Pro

Start Date

Start Date of a task is calculated as follows:

• If a custom field for "RQ Start DateTime" is specified in Gantt Configuration, its value from the Jira task will be used.
• If above is not true, then it will check in the database and get the "Start Date" value, if any.
• If above is not true, and if task 'Status' is 'In Progress', then it considers the date when it was converted from 'To Do' to 'In Progress' as the Start Date.
• If above not true, then it uses 'Created Date' as start date.
• If none of the above is true, then uses Today's date as start date.

Note: Once calculated, this Start date is used across all Programs where this task is referenced.

End Date

End Date of a task is calculated as follows:

• If a custom field for "RQ End DateTime" is specified in Gantt Configuration, its value from the Jira task will be used.
• If above is not true, then it will check in the database and get the "End Date" value, if any.
• If above is not true and if the issue's "Remaining Estimate" and "Time Spent" is available in time tracking fields they will be considered. The sum of "Remaining Estimate" and "Time Spent" is added to "Start Date" and the resultant value is set to "End Date" field.
• If above is not true and if "Original Estimate" is available, then the sum of "Original Estimate" and "Start Date" is set as "End Date".
• If above is not true and if 'Resolution' state is 'Resolved', then it considers Resolved Date as end date.
• If above not true, then it uses last updated and due date based on these conditions:
  • if updated date > due date date, then updated date is set as end date.
  • if updated date < due date date, then due date date is set as end date.

Note: Once calculated, this End date is used across all Programs where this task is referenced.

Sort Order

• If a custom field for "Sort Order" is specified in Gantt Configuration, its value from the Jira task will be used.
• If above is not true, then it will check in the database and get the "Sort Order" value, if any.
• If above is not true, then by default the value is assigned based on Rank.

Note: Sort Order will remain same for every project across Programs, if custom fields was configured. Else Sort Order will differ for every project across Programs.

Progress

• If a custom field for "Progress Percent" is specified in Gantt Configuration, its value from the Jira task will be used.
• If above is not true, then it will check in the database and get the "Progress percent" value, if any.
• If above is not true, then the value for progress has to be assigned manually in Gantt level.

Note: Progress percent remains same for project across Programs.

Indent Level

• If a custom field for "Parent Id" Custom field is specified in Gantt Configuration, its value from Jira task will be used.
• If above is not true, then it will check in the database and get the "Parent ID" value, if any.
• If the above is not true, then by default the sub-tasks will be assigned as child to its respective parent.

Note: Indent Level will remain same for every project across Programs, if custom fields was configured. Else Indent Level differs for every project across Programs.