Import from Tempo

Who: people with Manage the Jira sync. The Import from Tempo section appears on Admin → Jira sync once the sync finds worklogs made by Tempo, and stays while Tempo is connected.

Tempo saves its worklogs in Jira under its own app account, not the person's, so on their own they can't count in anyone's timesheet. Connecting Tempo lets LogQuill find each worklog's real author, and brings Tempo's accounts, work attributes and teams. Connecting only reads from Tempo: nothing changes in Tempo or in Jira.

Connect Tempo

Check, then import

Once connected, What would be imported lists what Tempo holds in three folding lists, each headed with what will happen ("4 accounts · 3 new · 1 to choose"). A list opens by itself while something in it waits for you. Each item is one line: its name, a short summary and a choice of what to do with it. Its arrow opens the rest (customer, lead, projects, members...):

• each Tempo account becomes an account, with its customer, lead, billable setting and projects. A starred project is one where the account is the default. An account whose lead isn't a LogQuill user gets you as its lead until you change it. A project that already has a default account keeps it.
• each work attribute becomes a worklog field, with its options, or the worklog's account. Attributes whose values come from outside Tempo aren't imported.
• each team becomes a team: its description, its lead as the team's leader, the people on it today, and its linked spaces (Jira's new name for projects) as the team's projects. Member roles, commitment, programs, permissions and timesheet approvals aren't imported, and the team has no country or type until you give it one. Its approvals follow the default: its leader, then HR as each absence type says.

For each account, field and team, choose:

• Merge into the one you already have: adds what it's missing (an account's projects, a list's options, a team's people and projects) and never removes anything. A merged team keeps its leader; Tempo's lead joins as a member.
• Import as new, under its own name, or with "(Tempo)" added when you already use the name.
• Don't import.

Something with no match here is imported as new unless you choose otherwise. One with the same name as yours waits for you to choose, marked in amber, and Import waits with it; Merge all and Import all as new settle everything waiting at once.

After an import, the list shows only what's left: what Tempo added since, and what you chose not to import, which stays Don't import until you choose otherwise. What was imported is counted, not listed again ("2 already imported"), and Import again brings what Tempo changed in it since.

A new team whose lead isn't a LogQuill user gets you as its leader; change it on the team after importing. Members who aren't LogQuill users, and links to anything but a space, are left out and listed on the team. Long lists of projects or members show the first five, then "and 12 more".

Choose Import. Tempo's worklogs then come in with the Jira sync, each under the person who logged it, with their account, billable hours and attributes.

While Tempo is connected

Every Jira sync brings Tempo's new worklogs and their changes. They stay read-only in LogQuill while Tempo is connected, as Tempo owns them. Import again brings accounts, attributes or teams added in Tempo since, and what Tempo changed in those already imported.

Disconnect

Disconnect makes LogQuill forget the token. Worklogs already imported stay, and can be edited in LogQuill from then on. New worklogs logged in Tempo stop coming in.