...
After connecting to the Jira instance you’re , you are ready to choose a project from the Jira Project drop-down menu under Jira Project. The list will include menu includes all of the projects that you have access to in the connected Jira instance. Once After you have selected the project is selected, you can set up the following filters for issue type, issue status and created date.:
Issue Type:Select the Issue Type you want to pull in: Task, Story, Bug, and Epic, or Select All. A task is created for selected Issue Types. Pull in hierarchical issues as tasks to capture estimates or the time tracked for those tasks.
Issue Status:Select the status of the Issue Type you want to pull in. The available statuses depend on the configuration of your Jira project.
Include issues created after: Choose a date to include only issues created after that date.
Depending on the filters that you choose, the Issue Count and User Count will update accordingly. The Issue Count in the lower left corner tells you the number of Jira issues that will come in as LiquidPlanner tasks when set up is complete. The User Count shows you a count of how many new users will be pulled in when set up is complete.
...
5 | Sync Settings |
...
In Sync Settings, you can choose your preferred option from the Pull Worklogs drop-down. how you want to pull hierarchies and work logs into LiquidPlanner. The following settings are available:
Reorder Jira Issues by LiquidPlanner Priority
This setting will reorder the tasks in your Jira project to reflect the priority order of your tasks in LiquidPlanner. Remember that in LiquidPlanner, tasks are prioritized from top to bottom, with the top being the highest priority and the bottom being the lowest. The setting is enabled by default. Deselect the check box if you do not want to send LiquidPlanner priority order to Jira.
Subfolder Organization
This setting determines how tasks are displayed when you pull them in. Tasks are displayed as a flat list if no Epics or custom hierarchy levels exist. The following options are available:
Flat list: Pulls tasks in a flat list in the project. Tasks are not sorted into folders.
Epic-Based Sub-folders: Creates a sub-folder for each Epic (level 1) with their issue (child) tasks inside the folder. If an issue does not belong to an Epic then it resides at the top level (the same level as the folders).
Hierarchical Sub-folders: Creates a sub-folder for each custom hierarchical issue type. An example would be for level 1 and above, such as for an Initiative, Feature, and Epic, with child items nested within the corresponding type. This option will only display if the instance you have selected is on a Jira Premium or Enterprise subscription.
Important: The subfolder organization is a one-way process after you set up the integration. After integration, you can change a flat list to Epic-Based and change Epic-Based to Hierarchical, but you cannot revert an option to the previous one. To change the subfolder organization, select the Integration button in your project and then select Modify Setup. There, you can modify your selection and save your changes, which take effect the next time you sync.
Pull Worklogs
The following options are available and will vary depending on your instance:
Do Not Pull any Worklogs: No Worklogs (Time Entries) are pulled into LiquidPlanner.
Pull from Jira: Pull Worklogs (Time Entries) from Jira into LiquidPlanner.
Pull from Tempo Timesheets: Pull Tempo Timesheet entries into LiquidPlanner. This option only displays if Tempo Timesheets is installed on your instance.
Cost Code: Select a cost code that is applied to Jira time entries in the selected project. This option only displays after you select to pull from either Jira or Tempo Timesheets. Note: After you select a cost code and complete the integration, you cannot change the cost code.
...
At this last step, Launch closes the integration window and creates a new project instantly, with tasks generated shortly after the sync completes. You may navigate away from the project while the sync is in progress.
9 | Sync and Modify Setup |
...
Example of Integration Organized by Flat List
When a project has been pulled in from Jira, it can be synced and modified through the drop down menu under the Jira Integration button.
...
By selecting a task on the list and visiting the Properties, you can view additional data that was pulled in from Jira. You can view the Issue Key and select it to open the issue directly in Jira. Additional information includes the Project Name, Issue Type, Priority, and Epic fields.
Delete Folders or Tasks
You can also delete folders or tasks that have populated in LiquidPlanner. Deleting items in LiquidPlanner does not delete them in Jira and vice-versa. On your next sync, deleted items are re-created in LiquidPlanner if they match the filter criteria. Select the three-dot icon next to a Folder or Task and select Delete Sub-Folder or Task. Re-sync to make these items re-appear on your list.