Creating Data Content: Tasks and Sub-Tasks
You can add standard Jira issues using the app's interface. Depending on the platform and selected option, task can be recorded as a standard Jira Issue or Sub-Task Jira Issue.
Depending on the configuration of the app, your tasks might get updated or recalculated when added to a Program.
The app requires two points on the timeline (or two dates) to generate a task bar and determine the start and end points. Those points in time are the task's 'Start date" and 'End date' and are stored as 'Start date' and 'End date' custom fields by default.
If a Task with no Start and / or End Dates is added to the scope of a Program, the app will pick the Original Estimate value to calculate the duration and set the task's Start date to Creation date.
Following this logic, if no Original Estimate value is available the app will again use the creation date as Start Date and when the End Date is empty, then it picks the resolution date (if the issue was Resolved) instead. This usually means that a Task will be set as a 1-day duration starting on the Creation date. With Original Estimate mapped as the Start or End Dates, it will represent the duration of a Task.
As a consequence, in such a scenario, the "Auto bottom up" task mode will be applied to tasks with empty date fields to avoid data corruption when the task are structured automatically using presets.
In the case of Sprint and Version tasks synchronization, the "Auto top down" is used by default.
When Original estimate is set during the creation of task or a task with Original estimate is added to the Program the app can calculate the End date and populate the filed accordingly but only if two data fields are mapped in Task configuration.
Read more about the synchronization settings in the Task configuration section.
When structuring your data using Versions or Sprints there are two additional scenarios wich result in different outcome if a Program is being created and when the structure builders are enabled in an existing Program:
- Program created using presets (Advanced configuration - Program wizard) - if the tasks dates exceed the Version or Sprint dates and the "Auto top down" mode is selected, the tasks be WILL NOT BE aligned with the dates of the parent task (applies only to Versions and Sprints).
- Structure builders are enabled and a new task is added to the Program - in this case the children tasks will be aligned with the parent task if the "Auto top down" mode is selected.
|1||JIRA Task (issue)|
Create a new task using the task creation screen.
|2||Artificial Task||Create an Artificial Task which will be added to the list of tasks. Artificial tasks will not be visible in external platforms such as Jira or Trello.|
|3||Task Template||Create and add the the task list a list of Artificial tasks using. You will be required to create a template first using Task Template Creation menu in the Program Configuration.|
To use this option, make sure to select an existing task on the task list first.
|1||Gantt Sub-Task||Create a new task using the task creation screen. The newly added task will be indented under the selected task on the task list.|
|2||Jira Sub-Task||Create a new sub-task using the task creation screen. The newly added sub-task will be indented under the selected task on the task list.|
|3||Artificial Sub-Task||Create an Artificial Task which will be added to the list of tasks and indented under the selected task. Artificial tasks will not be visible in external platforms such as Jira or Trello.|
Before initiating creation of a new task, select any existing Gantt task on the list to set the 'Jira project' field. Also, the newly added task will start on the same date as the selected one
In case of Jira Sub-Task it is worth mentioning, that the Issue on which we click has to be capable of having a Sub-Task (meaning - it cannot be a Sub-Task itself). Learn more about creating issues and sup-tasks in Jira.