...
Make sure that Jira issues have met the criteria to be imported - see the list above.
Make sure that you have the Manage Plans permissions for the resources for which you're planning, otherwise their Jira issues will not be imported.
Select a filter in the Filter by field (see Filtering Resources) to display only the resources for whom you're planning.The Assignee in the Jira issues must match the resources who are displayed in the Resource Planning view to be able to import their Jira issues. For example, if you filter so that only the Lunar Labs team is displayed, then only Jira issues that match these team members are imported.
Click the Import button at the top-right. All Jira issues that are eligible to be imported are listed in the Import from Jira dialog according to the filter that you have selected. You can add a filter in this dialog, which doesn't affect the filters in the Resource Planning view.
If a filter you select doesn't appear here, it may be that you don't have Manage Plans permission for that team or resource.
Check the box for each issue you want to import, or check the box beside Jira Issue at the top of the list to select all issues, and then click Import.
Plans are created for each Assignee over the time periods that are determined by the Jira issue's Due date and Original Estimate data. The Due Date is the end date for the plan, then working backwards from that, the hours in the Original Estimate are divided over the working days as determined by the resource's Workload scheme. These plans are indicated by an Import icon and Tempo Planner keeps a connection (a mapping ID) between the plan and its corresponding Jira issue. The Import icon also appears next to the resource's name and will disappear once the page is refreshed.
By default, issues of imported plans will not appear in the Issues list. To include them in the Issues list, go to the Issue side panel, click on Settings 
and check the Include Jira imported plans box.
...
Click the Import button at the top-right.
In the Import from Jira dialog, click the Updates tab. A notification appears on this tab with the number of updates to indicate that at least one of the 3 relevant fields in an imported Jira issue (Assignee, Due Date, or Original Estimate) has changed since the issue was last imported. All the Jira issues that have changed are listed here.
Check the box for each issue you want to update, or check the box beside Jira Issue at the top of the list to select all issues.
Click the Update button to confirm that you want to update the plans from the selected Jira issues. Any current plans based on these Jira issues are updated with the change. For example, if a resource manager changes the Assignee from Amy to Erica in Jira and performs an update in the Resource Planner, then Amy's plan will be reassigned to Erica.
...
From the Weeks view in the Resource Planning view, Catherine uses the date picker to set the dates for the sprint. In this case, it's 2 weeks.
She also filters by TEAM so that she only views Lunar Labs' team members: since she's filtering in the Resource Planning view, she won't have to filter again when she goes to import the Jira issues.
Catherine is now ready to import the Jira issues into the Resource Planning view. She clicks on the Import button in the top-right corner. The Import from Jira dialog is already filtered by team because Catherine filtered for it in the Resource Planning view.
The list displays all Jira issues that are assigned to these team members and may not be part of the sprint, so she checks only the ones she wants to import.
Catherine clicks the Import button at the bottom, and a notification appears alerting her of the number of imported plans that have been created.
In the Resource Planner view, an icon appears next to the resources’ names to indicate that there are plans created from the imported Jira issues.
...
Catherine wants to make changes to the Original Estimate of a Jira issue.
She changes the Original Estimate value in Jira. When she returns to Planner and clicks Import, she notices that there is a notification on the Updates tab. She wants the change of estimate value to reflect in Planner so she clicks the Update button and selects the issues for the plans that she wants to update.
Catherine notices that Amy and David have been over-allocated. She wants to change the Due Date for her Jira ticket (PAR-36) in Planner to fix this.
She makes the changes to the plans in Planner because she doesn't think that it's necessary to make this change in Jira. When she drags PAR-36's plan, a notification window alerts her that the changes she makes in Planner will not be reflected in Jira. She decides to go ahead by clicking Edit plan anyway.
Analyzing Planner Data
...