![]() ![]() If you choose not to merge records, each time the import is executed, a new record will be added to the table.If you choose to merge records, each time the import is executed, only new records will be added to the table.This can be changed to any available table in the base. Select Table: Table will default to the active Table.All available issue types can be selected. Issue Type: Select issue type to import. ![]() Select Project: Select the Project from Jira Cloud that you would like to import into Airtable.To import issues of any type (tasks, sub-tasks, new features, bugs, epics, and improvements) from a project, you can either configure the options in the Issues tab or use custom JQL (Jira Query Language) for more complex selections. Save your API token: This is the code saved when creating the API Key under the Getting Started Section.from the drop next to the workspace name. Enter your Jira Workspace name: This is the name of your Jira implementation. ![]() Enter your email: Use the email address linked to the API Key created under the Getting Started Section.Follow the on-screen instructions to allow Airtable connect to Jira Cloud. When you first add the extension to your dashboard, the extension prompts you to connect to a Jira account. Getting started with the Jira Cloud extension Change “Only you and admins” to “Anyone”.On the Profile and Visibility page → Scroll to the bottom Contact section.Have each member of your project click on their Profile Icon → Account Settings.Individual users need to manually change their settings by going to the Profile and visibility page and changing the email visibility option (see image below). NOTE: “Public" is the only supported option at this time. If you’re an admin, you can click on “Jira System settings” and enable the ability to pull in assignees by changing the user email visibility from “Hidden” to “Public” inside your organization. It should take less than a minute to adjust these settings. You can either have an admin change these settings globally or ask each of your project members to change their personal settings. It does not change any project-specific privacy settings, like who can view or access your project. This change only alters who within your project can view the user email on the user profile page. To fully utilize the Assignee field, additional configuration in Jira Cloud is needed.ĭue to privacy limitations of the Jira API, users can only import assignee information after they enable user email visibility in Jira. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |