Once a Jira issue is imported, it's embedded inside a Sunsama task. This article explains how data flows between Jira and Sunsama and where you should do your work.
Imported tasks · 0:08
Once a Jira issue is imported into Sunsama, it becomes a Sunsama task, with an embedded Jira issue. You can identify a task that came from Jira via the Jira logo on the card.
Viewing Jira details · 0:28
Click on a Sunsama task that's linked to Jira to see a preview of your Jira issue embedded inside the Sunsama task.
Interacting with Sunsama specific task information · 0:21
Your associated Sunsama task acts like a worksheet for your Jira issue. Inside your Sunsama task, you can add notes, time tracking information, subtasks, and comments without messing with your Jira issue.
Use your Sunsama task to track the minutia of the task that your collaborators might not care about inside of Jira itself.
If your Jira issues encapsulate large amounts of work, you can import the Jira issue multiple times into Sunsama, and change the title of the imported task to reflect just the bit of work you'll do that day. You could also use subtasks for this.
Status syncing · 1:02
Sunsama allows you to hook into your Jira workflow and update the status of a Jira issue when you import the issue and when you check off the associated Sunsama task.
In both cases, you'll see a small dialog that allows you to update the status of the issue.
There's two typical use cases for this functionality:
- When importing a Jira issue, you'll change the status of the issue to "In Progress" (or the like).
- When completing a Jira issue, you'll change the status of the issue to "Completed" (or the like).
Updated about 1 year ago