Jira

you can send your flare alerts directly to jira here's how to configure flare and receive data in your jira workspace for detailed instructions, follow the storylane demo provided below creating a jira alert channel you will need to be have an admin role in your flare organization in order to configure this integration go to the integration hub click on configure then channel to create a new channel enter a name for your channel select "jira" as type fill in the following information server netloc the full domain of your jira server ex my company atlassian net email the email of the account associated with the api token api token the api token (create the api token here https //id atlassian com/manage profile/security/api tokens https //id atlassian com/manage profile/security/api tokens ) space key the project key is usually an uppercase version of your project name it can be found in the url of your project work type the value provided should be an exact match with what was created in jira labels these labels are added to every created issue the labels support formatting (see below) https //app archbee com/docs/zrhxxu3ros7eq2rifnjmk/vskqyyh1ipmu gqh4w ob#bl sx optionally, you can add additional custom fields to pass to jira when creating issues each entry takes a field key and a value multiple fields can be added using the add field button this setting enables support for jira service management for more information, see jira service management docid\ kxvmcnotecpsblk ypofr use the test channel button to ensure that the connection is successful after a successful test, click the create alert channel button to create the channel formatting dynamic formatting is supported for the following activity fields risk source type currently, formatting can only be used in the labels for example, a label value of flare ${risk} can result in labels such as flare high , flare critical , etc viewing alerts in jira here is what a resulting flare alert will look like in jira this example is from a telegram chat message jira service management flare supports jira service management (jsm) alert channels jsm requires a request type to be set when creating issues, which is configured using the custom fields option when setting up the channel each custom fields entry takes a field key and a value for jsm, the field key is the custom field id that corresponds to request type in jira follow these steps to find the correct values for your instance find the custom field id go to the following url, replacing \<work item id> with the id of any existing issue in your project https //\<your domain> atlassian net/rest/api/3/issue/\<work item id>?expand=names in the response, extract the customfield xxxxx key from fields issuetype name where the value is request type also note the `id` value of the issue, which you will need for the next step find the portal key and request type key go to the following url, replacing \<issue numerical id> with the `id` value from step 1 above https //\<your domain> atlassian net/rest/servicedesk/1/servicedesk/request/\<issue numerical id>/request types extract the portalkey and key from the request type you would like to use with flare combine them as \<portalkey>/\<key> and enter those values as custom fields in the jira alert channel for more detail on these api calls, see set the request type when creating an issue using rest api in jsm cloud https //support atlassian com/jira/kb/set the request type when creating an issue using rest api in jsm cloud/ in the atlassian support documentation related articles