Note: you must be an administrator to perform the following

Create, import, and manage Jira issues from Fellow. This integration can be helpful to all teams in your organization such as the Engineering team, Design team, etc. With this integration, you can use Fellow for planning high-level action items from within your 1-on-1s and team meetings, while doing more granular project management using your existing workflows in Jira.

From the settings tab, you can set configuration options for how Fellow will interact with different projects within Jira. Once you add a project, you'll be able to toggle additional settings that allow you to control what information flows between action items in Fellow and linked Jira issues.

This per-project setting defines whether Fellow will keep the title, due date, and assignee of any linked Jira issues in sync with Fellow. If this option is enabled, any changes to the action item text, due date, or assignee inside Fellow will automatically propagate to the linked Jira issue. Similarly, any changes to a linked Jira issue will automatically sync back to Fellow. When this option is disabled, changes will not propagate beyond the point at which the issue was linked.

Note: that Fellow will sync assignees based on email address. If the Fellow assignee does not exist as a Jira user, the assignee will not sync. Similarly, if the assignee within Jira changes to someone who does not have access to the Note series on Fellow, the assignee will not sync.

From Jira settings, you can enable Push status for your workspace. When enabled, checking off your action item in Fellow will also change the status of that item in Jira. You can map Fellow's action item statuses to your Jira project to control what the status will change to in Jira. When Push status is off, checking an item off in Fellow won't have any effect on the Jira issue, and you won't be able to map your status.