Installing and setting up

1. Install EA Sphere from the Atlassian Marketplace. A Jira administrator approves the permissions listed in the security statement.
2. Open EA Sphere from the Apps menu. On first use, a Jira administrator chooses between loading the sample company, which demonstrates every function with realistic data, and starting with an empty catalog. Until then, other people can open EA Sphere but cannot add records. Later, under Settings, Data, an administrator can replace all data with the sample data set, which also replaces the settings with the sample's, or delete all data, settings included.
3. Complete the settings in this order, because each step provides values the next one uses: General; Reference lists; Recovery tiers; Data quality; Degradation, including change freeze windows, sender groups and communication audiences; Continuity; and Jira, where incident and mitigation spaces are chosen.
4. Add records with Add system, bulk add a list of names from the catalog, or import a CSV file under Settings, Data, either by choosing the file or by pasting its text. A row whose name matches an existing record updates that record. In the Hosted on and upstream dependency columns, record names are separated by semicolons; a name that itself contains a semicolon is kept whole when it matches a record or a row in the file. The catalog's CSV export puts any list item that contains a semicolon in quotes, so an exported file imports back as it was, except that a value renamed in Settings since the export is taken under its new name. After an import, EA Sphere reports how many records it created, updated and left unchanged, and lists any values it could not use, such as a tier that is not defined, a date it cannot read or a row without a name, and any incomplete records it created for hosts and dependencies that are not rows in the file. If some records were not recorded for any other reason, EA Sphere reports the import as not complete: the dialog keeps the file and says how many, and the file can be imported again. List values are compared the way Settings compares them, so a type written in full-width letters is the existing type. A row whose name someone else created while the import ran is not imported: EA Sphere reports the import as not complete and names the record, the file stays in the dialog, and importing it again updates that record. Dates can be written as YYYY-MM-DD or MM/DD/YYYY.