Jira Import, Replay, Sync

You can import your Jira Cloud projects into Socratic. If you use epics in Jira, these are converted automatically into Socratic objectives.

You have three options when importing from Jira:

1. Standard import, in which a Jira project is simply converted to a Socratic workstream, with its issues and epics turned into tasks and objectives, respectively.

2. Replay (beta), in which in addition to (1), the history of work in your Jira Cloud projects is ‘replayed’ through Socratic’s intelligence, as though all the work had occurred in Socratic. For instance, by running Jira Replay, you could see your average delivery time—for a specific project, or for your organization as a whole—derived from historical actuals in Jira.

3. Sync (beta), for cases where you want to use Jira and Socratic together. Here, we provide bi-directional synchronization for the creation and movement of Jira issues and Socratic tasks.

Both Jira Replay and Jira Sync are beta offerings. You can choose to use either or both at time of import. Neither can be applied to a workstream retroactively. Their functionality is described in further detail below.

Note that the Jira integration requires Administer Jira global permissions (Jira admin).

Activate Jira integration (Jira Sync, Jira Replay)

1. Click the Socratic icon at top left, and choose Integrations:

Open app settings

2. Click on Jira. Connect to your Jira Cloud instance:

The tooltips provide links to the necessary screens in Jira

3. Map Jira users to Socratic users. When mapping users, you can choose to map to existing users in Socratic, create a new user in Socratic, or not to map a Jira user at all. If imported Jira issues don’t have a matching assignee in Socratic, we mark those issues as "Unassigned" in Socratic.

Importing projects

1. Click Workstreams in the left sidebar. Then click the Import button in the upper right:

Import projects from Jira

2. Choose a Jira project to import.

3. Confirm the order of your Jira statuses. Note that issues in a Jira status of To Do are mapped to Socratic’s backlog work phase. You can also rename work phases and their order following import.

The time to import a Jira project depends on the size of the project, and whether Replay has been activated. Larger projects may take ten minutes or more. You can use Socratic while the import runs.

The following are not available for import from Jira:

• Images and attachments

• Issue labels

• Issue comments

Jira Replay (beta)

With Replay, you’ll see your Jira data as though the work for that project had occurred in Socratic. This means you can see all of Socratic's work health intelligence—forecast, average historical efforts, workload distribution—built entirely from your Jira record.

Note that Socratic’s Trends will also populate, based on our analysis of the history of your work activity in Jira. In the case of a standard import, without Replay, Trends will show as empty until you begin accumulating work activity in Socratic.

Socratic’s Jira Replay may surface cases of low hygiene in Jira work activity. For example, if you have a sizable number of Jira issues orphaned in active states, that may produce unnaturally long effort estimates in Socratic.

In the event low Jira hygiene is impacting the reliability of data in Socratic, you can simply archive the imported project, and re-import without Replay:

Archiving a workstream

Jira Sync (beta)

Sync mirrors the primary work activity between a Jira project and a Socratic workstream. This mirroring is bi-directional. In other words, an action taken with a Jira issue is reflected in the corresponding Socratic task, and vice versa.

The specific actions we mirror between a Jira project and Socratic workstream:

• Creation of a task / issue.

• Movement of a task / issue.

• Assignment (or reassignment) of a task / issue.

• Changes to task / issue title or description.