You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Jira Server integration is much more useful and much easier for org administrators to administer if the Provider can be configured at the Organization level. Today, the mutation (and the shape of its parameter) don't allow for this, even though the underlying data architecture does.
Acceptance Criteria (optional)
Administrators can:
Can run a GraphQL query via the administration interface to add an org scoped Jira Server/Jira Data Center Provider
" to remove a Jira Server/Jira Data Center Provider
Users can:
Use the Team Settings->Integrations menu (and other interfaces) in order to add Jira Server/Jira Data Center to their team
Parabol Customer Success:
Can refer to an internal Notion document on how to help users add their org-scoped Provider
jordanh
changed the title
Integrations: Enhance AddIntegrationProvider to add org-scoped Jira Server Provider(s)
Jira Server: Enhance AddIntegrationProvider to add org-scoped Provider(s)
May 29, 2024
jordanh
changed the title
Jira Server: Enhance AddIntegrationProvider to add org-scoped Provider(s)
Jira Server: Enhance Add/RemoveIntegrationProvider to add org-scoped Provider(s)
May 29, 2024
This already works. An integration provider is always added to a team, but can be scoped to an org, i.e. the whole org where the team lives has access to the integration provider. See also discussion on #6014.
Issue - Enhancement
The Jira Server integration is much more useful and much easier for org administrators to administer if the Provider can be configured at the Organization level. Today, the mutation (and the shape of its parameter) don't allow for this, even though the underlying data architecture does.
Acceptance Criteria (optional)
Administrators can:
Users can:
Parabol Customer Success:
Estimated effort: 5 points (see CONTRIBUTING.md)
The text was updated successfully, but these errors were encountered: