v2.22: Your text is safe with Jira

Fixes from a full review of Sprintwise's code: imports and Jira never quietly lose or overwrite anyone's work.

• Re-importing: a file with fewer columns (say, only Key, Summary and Status) leaves the descriptions, criteria and points already saved as they are.
• Send to Jira:
  • It sends only what you edited here.
  • It never sends a field back over a newer change a teammate made in Jira. If you both changed the same field, it tells you instead.
• Criteria into a Jira description: writing them no longer removes the code, tables, panels or notes that follow.
• Finished issues: stories finished in Jira are finished here after a Sync, even when the search leaves finished issues out.
• Stories edited here: they still take Jira's status and any change to fields you didn't edit. Points or criteria that Jira won't take stay edited, so Sync doesn't undo them. Points go to the story points field the issue actually uses.
• Left-out issues: issues unticked at import, or deleted here, stay out of later syncs.
• Sprint log: moving criteria between the description and the criteria field no longer shows as a change.
• Nightly sync:
  • It records why a project failed.
  • It carries on with the other projects.
  • It can't run past its time limit.
• Jira connection: reconnecting with a different Atlassian account replaces the old connection.
• Snapshots: they're limited by stored text and by how many you can save in a few minutes.
• Re-scoring: it's faster, and scores always use the latest settings. Rules version 6.

Note: this release broke every Jira action. v2.22.1 fixes it, so use v2.22.1.