Asana for Jira FAQ
How does the authorization model work?
- The integration uses OAuth as the Authorization standard. Users will remain authenticated until the OAuth token expires or until someone revokes that token.
- In order to link existing Jira issues to an Asana task or to create a new Jira issue from Asana you need to be authorized into your Jira account.
How do permissions work?
- When creating a new Jira issue from Asana, the integration follows Jira’s permission model. So a user can only create a Jira issue if they have permission to do so in Jira. This is the only scenario where a user can write data into Jira (in order to create a new Jira issue). Similarly, this is also the only scenario where the integration reads Asana data.
How does the integration work with Asana?
-
The integration reads Asana data, and creates a new Jira issue by writing (optional) some of the Asana task data (task name, description, and attachments) into the new Jira issue’s fields (issue name, etc).
-
Similarly users can only link existing Jira issues to an Asana tasks if: they’re authorized into their Jira account and they have access to those specific Jira issues in Jira.
-
Once an issue has been linked to an Asana task, then the read permissions are controlled by Asana’s permissions model. For example, if a user links a Jira issue to task XYZ, then Asana users with access to Asana task XYZ can see (read-only) the linked Jira issue’s data. If you want to keep the Jira data private within Asana, you can make your projects or tasks private.