Connect and select projects
An administrator opens Settings → Integration connections, adds a Jira Cloud connection and gives it a name. Open Configuration, choose Connect with Atlassian, grant access and select the Jira site. Discover projects, tick only participating projects, enable and save. Test the connection. Multiple Jira connections, including connections to the same site, are supported alongside Monday.
Your Jira account must be able to browse selected projects and their issues under Jira's issue security rules. An Atlassian administrator may need to allow the app. Email addresses may be hidden by Jira profile privacy; mappings still use stable account IDs.
Server OAuth setup
The server owner creates one OAuth 2.0 (3LO) app in the Atlassian developer console. Add the Jira API permissions read:jira-work and read:jira-user; authorisation requests also use offline_access for rotating refresh tokens. Enable OAuth, register the exact public HTTPS callback /jira/callback, and enable distribution for other authorised users as required by Atlassian.
Configure Jira:ClientId, Jira:ClientSecret and Jira:RedirectUri using server secrets or environment configuration (double underscores instead of colons). Do not put the client secret in source control. Preserve the application's data-protection key ring. No individual customer OAuth app or API token is needed. A local development callback may use HTTP on localhost if registered with Atlassian.
Users and work
Discover users from the connection's selected work, then explicitly map them to existing team members. Discovery includes assignees and reporters, not every Jira account. Mapping never creates people or silently assigns scheduled work.
From Projects → Add work, choose the named Jira connection and search summaries. Review a work item and enter local effort and scheduled people. Source time-tracking estimates prefill effort where available; missing effort must be supplied explicitly. Story points and custom estimation fields are not converted into time. Due dates, source assignee, status, type and parent are displayed as source information. Child work appears as stage suggestions to review separately.
Refresh and ownership
Use Refresh from Jira on a linked project. Source title, description, workflow status, assignment, time estimates and due date are refreshed. Local stage effort, assignments, dates, prerequisites and calculated scheduling are retained. Jira statuses are shown verbatim; they do not silently mark local stages Done.
Refresh and discovery run on demand. There is no background polling or webhook registration. Search shows the first 100 matches; narrow the summary search for more. Complete project discovery is bounded at 5,000 projects and user/child-work discovery at 5,000 work items. Incomplete discovery is rejected without replacing mappings. Respect rate-limit messages before retrying. Reconnect after revoked or expired authentication.
Safe disconnect and limitations
Disabling retains credentials. Disconnecting clears credentials while retaining projects, stages, mappings, planning and Activity history. A connection remains pinned to its original Jira site, even after disconnect; use a new connection for another site.
This connector reads Jira Cloud only. It does not change Jira dates, estimates, statuses, assignees, worklogs or comments. Monday's personal meeting updates remain a Monday capability. Jira Server/Data Center, custom estimation fields, automatic status translation and automatic dependency import are not supported.