![]() Switch to another browser (Chrome, Edge, and so on) to configure correctly.Īfter you prepare this integration in Jira, you will need these artifacts to add the integration in Citrix Workspace Microapps: ![]() Configuring this microapp with Internet Explore 11 will result in errors. Jira no longer supports Internet Explorer 11. Navigate to, log in if necessary, in Contact section and next to the email account select Anyone under the Who can see this? menu. ![]() This means service accounts as well as the accounts that users log in to Citrix Workspace through OAuth. Review prerequisitesĪll user accounts that you want to use through this integration must have visibility for their email in account settings set to Anyone. For full details of the microapps available in each integration, see Use Jira microapps. The HTTP integration provides more power to configure the cached data structure. We recommend using the newer HTTP integration for most use-cases. We provide two Jira integration templates for your use. After you complete this process, your existing level of audit logging persists, including any actions carried out by the use of Citrix Microapps. Use the following process to enable the integration with Jira. Integrate with Jira to track issues and get automated updates about tasks on any device, intranet, or messenger. Questo articolo è stato tradotto automaticamente. (Aviso legal)Įste artigo foi traduzido automaticamente. (Clause de non responsabilité)Įste artículo ha sido traducido automáticamente. (Haftungsausschluss)Ĭe article a été traduit automatiquement. This article has been machine translated.ĭieser Artikel wurde maschinell übersetzt. Questo contenuto è stato tradotto dinamicamente con traduzione automatica. (Aviso legal)Įste texto foi traduzido automaticamente. (Clause de non responsabilité)Įste artículo lo ha traducido una máquina de forma dinámica. (Haftungsausschluss)Ĭet article a été traduit automatiquement de manière dynamique. This content has been machine translated dynamically.ĭieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. If you need to override the automatic discovery, you can define the following block in your Cortex Catalog Descriptor.Integration template connector specificationsĮxport and import integrations and microappsĬreate integration data structures in depthĬreate a new microapp for a template integrationĬustomize an existing microapp for a template integrationĬreate a new microapp for a custom integration that you built using the HTTP Connector If your Jira labels/components/projects don’t cleanly match the Cortex entity tag, you can override this in the Cortex Catalog Descriptor. For example, if your entity tag is “my-service”, then the corresponding tickets in Jira should have “my-service” as a label, component, or project. Registration Discovery īy default, Cortex will tie Jira tickets by looking for any tickets where the label, component, or project field on the issue includes the Cortex entity tag (e.g. Once the link is created, add your Jira host, client ID, and client secret under Settings → Jira by selecting On-Prem (OAuth) in the dropdown and filling out the form. Copy the client ID and client secret for the created link.For the Permission, select "Write" and click save.For the redirect url, put in the url of your cortex instance + /oauth/internal/jira.For the application type pick "External" and for the direction select "Incoming".In your Jira server go to the Settings -> Applications -> Application Links -> Create Link.In order to do so you will need to follow these steps to set up an application link If running a self-hosted Jira instance (requires Jira Server version 8.22 or higher) you can also use OAuth to connect to Jira. Add your Jira host, username, and password under Settings → Jira by selecting On-Prem (Basic Auth) in the dropdown. If running a self-hosted Jira instance, you can use basic auth to connect to Jira. If you're unable to directly whitelist our static IP, you can route requests through a secondary proxy in your network that has this IP whitelisted, and have that proxy route traffic to your Jira instance. ![]() Reach out to support at to receive details about our static IP. We route our requests through a static IP address. If you're using a self-hosted instance of Jira, you'll need to verify that your Cortex instance is able to reach the Jira instance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |