Atlassian Jira On Premise

the atlassian jira on premise connector allows for automated issue tracking and project management within the swimlane turbine platform atlassian jira on premise is a powerful issue and project tracking tool widely used by development and operations teams the swimlane turbine connector for jira on premise enables users to automate the creation, updating, and management of jira issues, enhancing collaboration and incident response by leveraging this integration, teams can attach files, add comments, transition issues, and execute searches within jira directly from the swimlane platform, streamlining workflows and reducing manual effort atlassian jira on premise connector integrates with swimlane to allow creating, editing, retrieve, search issues and add and delete attachments prerequisites to utilize the atlassian jira on premise connector, ensure you have the following prerequisites http basic authentication with these parameters url the base url of your jira instance username your jira username api token a jira api token used in place of a password for increased security http bearer authentication with these parameters url the base url of your jira instance personal access token (pat) a personal access token for bearer token authentication capabilities this connector provides the following capabilities add attachment add comment create issue delete attachment edit issue get attachment get comments get issue get issuetypes get issue transitions issue transition search input details add attachment this resource expects a multipart post the media type multipart/form data is defined in rfc 1867 most client libraries have classes that make dealing with multipart posts simple for instance, in java the apache http components library provides a http //hc apache org/httpcomponents client ga/httpmime/apidocs/org/apache/http/entity/mime/multipartentity html that makes it simple to submit a multipart post in order to protect against xsrf attacks, because this method accepts multipart/form data, it has xsrf protection on it this means you must submit a header of x atlassian token no check with the request, otherwise it will be blocked the name of the multipart/form data parameter that contains attachments must be "file" create issue the fields that can be set on create, in either the fields parameter or the update parameter can be determined using the /rest/api/2/issue/createmeta resource if a field is not configured to appear on the create screen, then it will not be in the createmeta, and a field validation error will occur if it is submitted creating a sub task is similar to creating a regular issue, with two important differences the issuetype field must correspond to a sub task issue type (you can use /issue/createmeta to discover sub task issue types), and you must provide a parent field in the issue create request containing the id or key of the parent issue the updatehistory param adds the project that this issue is created in, to the current user's project history, if set to true (by default, the project history is not updated) example { "update" { "worklog" \[ { "add" { "timespent" "60m", "started" "2011 07 05t11 05 00 000+0000" } } ] } } or { "fields" { "project" { "id" "10000" }, "summary" "something's wrong", "issuetype" { "id" "10000" }, "assignee" { "name" "homer" }, "reporter" { "name" "smithers" }, "priority" { "id" "20000" }, "labels" \[ "bugfix", "blitz test" ] } } edit issue the issue can either be updated by setting explicit the field value(s) or by using an operation to change the field value the fields that can be updated, in either the fields parameter or the update parameter, can be determined using the /rest/api/2/issue/{issueidorkey}/editmeta resource if a field is not configured to appear on the edit screen, then it will not be in the editmeta, and a field validation error will occur if it is submitted specifying a "field id" field value in the "fields" is a shorthand for a "set" operation in the "update" section field should appear either in "fields" or "update", not in both example { "update" { "summary" \[ {"set" "bug in business logic"} ], "components" \[ {"set" "some component"} ] } } or { "fields" { "summary" "this is a shorthand for a set operation on the summary field", "components" "some component" } } get issue an issue json consists of the issue key, a collection of fields, a link to the workflow transition sub resource, and (optionally) the html rendered values of any fields that support it (e g if wiki syntax is enabled for the description or comments) the fields param (which can be specified multiple times) gives a comma separated list of fields to include in the response this can be used to retrieve a subset of fields a particular field can be excluded by prefixing it with a minus by default, all ( all) fields are returned in this get issue resource note the default is different when doing a jql search the default there is just navigable fields ( navigable) for more details, please refer to notes section of get issue search sorting the jql parameter is a full jql expression, and includes an order by clause the fields param (which can be specified multiple times) gives a comma separated list of fields to include in the response this can be used to retrieve a subset of fields a particular field can be excluded by prefixing it with a minus by default, only navigable ( navigable) fields are returned in this search resource note the default is different in the get issue resource the default there all fields ( all) for more details, please refer to notes section expanding issues in the search result it is possible to expand the issues returned by directly specifying the expansion on the expand parameter passed in to this resources for instance, to expand the "changelog" for all the issues on the search result, it is neccesary to specify "changelog" as one of the values to expand issue transition the fields that can be set on transition, in either the fields parameter or the update parameter can be determined using the /rest/api/2/issue/{issueidorkey}/transitions?expand=transitions fields resource if a field is not configured to appear on the transition screen, then it will not be in the transition metadata, and a field validation error will occur if it is submitted the updatehistory param adds the issues retrieved by this method to the current user's issue history, if set to true (by default, the issue history does not include issues retrieved via the rest api) you can view the issue history in the jira application, via the issues dropdown or by using the lastviewed jql field in an issue search example { "transition" { "id" "41" } } notes https //docs atlassian com/software/jira/docs/api/rest/9 13 0/ https //docs atlassian com/software/jira/docs/api/rest/9 13 0/#api/2/issue getissue https //docs atlassian com/software/jira/docs/api/rest/9 13 0/#api/2/search search configurations atlassian jira on prem http basic authentication authenticates atlassian jira on prem using username and password configuration parameters parameter description type required url a url to the target host string required username username string required password api token string required verify ssl verify ssl certificate boolean optional http proxy a proxy to route requests through string optional jira server pat authentication authenticates using bearer token such as a jwt, etc configuration parameters parameter description type required url a url to the target host string required token personal access token string required verify ssl verify ssl certificate boolean optional http proxy a proxy to route requests through string optional actions add attachment attach files to a specified jira issue using the issueidorkey requires path parameters and form data endpoint url /rest/api/2/issue/{{issueidorkey}}/attachments method post input argument name type required description path parameters issueidorkey string required parameters for the add attachment action headers object optional http headers for the request headers x atlassian token string optional http headers for the request form data object required response data form data file array required response data form data file file name string required response data form data file file string required response data input example {"path parameters" {"issueidorkey" "10000"},"headers" {"x atlassian token" "no check"},"form data" {"file" \[]}} output parameter type description status code number http status code of the response reason string response reason phrase output example {"status code" 200,"reason" "ok","response headers" {},"json body" \[{"self" "http //www example com/jira/rest/api/2 0/attachments/10000","filename" "picture jpg","author" {},"created" "2024 01 22t19 59 47 624+0000","size" 23123,"mimetype" "image/jpeg","content" "http //www example com/jira/attachments/10000","thumbnail" "http //www example com/jira/secure/thumbnail/10000"}]} add comment adds a new comment to a specified issue in atlassian jira on premise, requiring the issue id or key and author details endpoint url /rest/api/2/issue/{{issueidorkey}}/comment method post input argument name type required description path parameters issueidorkey string required parameters for the add comment action parameters expand string optional parameters for the add comment action id string optional unique identifier author object optional parameter for add comment author name string optional name of the resource author key string optional parameter for add comment author emailaddress string optional parameter for add comment author avatarurls object optional url endpoint for the request author displayname string optional name of the resource author active boolean required parameter for add comment author timezone string optional parameter for add comment body string optional request body data renderedbody string optional request body data updateauthor object optional parameter for add comment updateauthor name string optional name of the resource updateauthor key string optional parameter for add comment updateauthor emailaddress string optional parameter for add comment updateauthor avatarurls object optional url endpoint for the request updateauthor displayname string optional name of the resource updateauthor active boolean required parameter for add comment updateauthor timezone string optional parameter for add comment created string optional parameter for add comment updated string optional parameter for add comment visibility object optional parameter for add comment visibility type string optional type of the resource input example {"parameters" {"expand" "renderedbody"},"path parameters" {"issueidorkey" "10000"}} output parameter type description status code number http status code of the response reason string response reason phrase self string output field self id string unique identifier author object output field author author self string output field author self author name string name of the resource author displayname string name of the resource author active boolean output field author active body string request body data updateauthor object output field updateauthor updateauthor self string output field updateauthor self updateauthor name string name of the resource updateauthor displayname string name of the resource updateauthor active boolean output field updateauthor active created string output field created updated string output field updated visibility object output field visibility visibility type string type of the resource visibility value string value for the parameter output example {"status code" 201,"reason" "ok","response headers" {},"json body" {"self" "http //www example com/jira/rest/api/2/issue/10010/comment/10000","id" "10000","author" {"self" "http //www example com/jira/rest/api/2/user?username=fred","name" "fred","displayname" "fred f user","active"\ false},"body" "lorem ipsum dolor sit amet, consectetur adipiscing elit pellentesque eget venen ","updateauthor" {"self" "http //www example com/jira/rest/api/2/user?username=fred","name" "fred","displayname" "fred create issue create an issue or sub task in atlassian jira on premise using a json representation with required 'fields' data endpoint url /rest/api/2/issue method post input argument name type required description parameters updatehistory boolean optional if true then the user's project history is updated fields object optional parameter for create issue fields summary string required parameter for create issue fields parent object optional parameter for create issue fields parent key string optional parameter for create issue fields issuetype object required type of the resource fields issuetype id string required unique identifier fields components array optional parameter for create issue fields components id string optional unique identifier fields project object required parameter for create issue fields project id string required unique identifier fields description object optional parameter for create issue fields description type string optional type of the resource fields description version number optional parameter for create issue fields description content array optional response content fields description content type string optional type of the resource fields description content content array optional response content fields description content content text string optional response content fields description content content type string optional type of the resource fields reporter object optional parameter for create issue fields reporter id string optional unique identifier fields fixversions array optional parameter for create issue fields fixversions id string optional unique identifier fields priority object optional parameter for create issue fields priority id string optional unique identifier input example {"parameters" {"updatehistory"\ false},"json body" {"fields" {"summary" "issue summary","parent" {"key" "sct 214"},"issuetype" {"id" "10000"},"components" \[{"id" "10000"}],"project" {"id" "11435"},"description" {"type" "doc","version" 1,"content" \[{"type" "paragraph","content" \[{"text" "order entry fails when selecting supplier ","type" "text"}]}]},"reporter" {"id" "5b10a2844c20165700ede21g"},"fixversions" \[{"id" "10001"}],"priority" {"id" "20000"},"labels" \["bugfix","blitz test"],"timetracking" {"remainingestimate" "5","originalestimate" "10"},"security" {"id" "10000"},"environment" {"type" "doc","version" 1,"content" \[{"type" "paragraph","content" \[{"text" "uat","type" "text"}]}]},"versions" \[{"id" "10000"}],"duedate" "2019 05 11","assignee" {"id" "5b109f2e9729b51b54dc274d"}}}} output parameter type description status code number http status code of the response reason string response reason phrase id string unique identifier key string output field key self string output field self output example {"status code" 201,"reason" "ok","response headers" {},"json body" {"id" "10000","key" "tst 24","self" "http //www example com/jira/rest/api/2/issue/10000"}} delete attachment removes a specified attachment from an issue in atlassian jira on premise using the attachment's unique id endpoint url /rest/api/2/attachment/{{id}} method delete input argument name type required description path parameters id string required parameters for the delete attachment action input example {"path parameters" {"id" "10000"}} output parameter type description status code number http status code of the response reason string response reason phrase output example {"status code" 204,"reason" "removal was successful","response headers" {},"json body" {}} edit issue edits an existing issue in atlassian jira on premise using the specified issue id or key and a json payload endpoint url /rest/api/2/issue/{{issueidorkey}} method put input argument name type required description path parameters issueidorkey string required parameters for the edit issue action parameters notifyusers boolean optional parameters for the edit issue action historymetadata object optional response data historymetadata actor object optional response data historymetadata actor avatarurl string optional response data historymetadata actor displayname string optional response data historymetadata actor id string optional response data historymetadata actor type string optional response data historymetadata actor url string optional response data historymetadata extradata object optional response data historymetadata extradata iteration string optional response data historymetadata extradata step string optional response data historymetadata description string optional response data historymetadata generator object optional response data historymetadata generator id string optional response data historymetadata generator type string optional response data historymetadata cause object optional response data historymetadata cause id string optional response data historymetadata cause type string optional response data historymetadata activitydescription string optional response data historymetadata type string optional response data update object optional date value update summary array optional parameter for edit issue update summary set string optional parameter for edit issue update components array optional parameter for edit issue input example {"parameters" {"notifyusers"\ true},"json body" {"historymetadata" {"actor" {"avatarurl" "http //mysystem/avatar/tony jpg","displayname" "tony","id" "tony","type" "mysystem user","url" "http //mysystem/users/tony"},"extradata" {"iteration" "10a","step" "4"},"description" "from the order testing process","generator" {"id" "mysystem 1","type" "mysystem application"},"cause" {"id" "myevent","type" "mysystem event"},"activitydescription" "complete order processing","type" "myplugin\ type"},"update" {"summary" \[{"set" "bug in business logic"}],"components" \[{"set" ""}],"timetracking" \[{"edit" {"remainingestimate" "4d","originalestimate" "1w 1d"}}],"labels" \[{"add" "triaged"},{"remove" "blocker"}]},"fields" {"summary" "completed orders still displaying in pending","customfield 10010" 1,"customfield 10000" {"type" "doc","version" 1,"content" \[{"type" "paragraph","content" \[{"text" "investigation underway","type" "text"}]}]}},"properties" \[{"value" "order number 10784","key" "key1"},{"value" "order number 10923","key" "key2"}]},"path parameters" {"issueidorkey" "10002"}} output parameter type description status code number http status code of the response reason string response reason phrase response text string output field response text output example {"response text" "string"} get attachment retrieve metadata for a specified attachment in atlassian jira on premise using the attachment id endpoint url /rest/api/2/attachment/{{id}} method get input argument name type required description path parameters id string required the id of the attachment input example {"path parameters" {"id" "10033"}} output parameter type description status code number http status code of the response reason string response reason phrase id number unique identifier self string output field self filename string name of the resource author object output field author author self string output field author self author accountid string unique identifier author avatarurls object url endpoint for the request author avatarurls 48x48 string url endpoint for the request author avatarurls 24x24 string url endpoint for the request author avatarurls 16x16 string url endpoint for the request author avatarurls 32x32 string url endpoint for the request author displayname string name of the resource author active boolean output field author active created string output field created size number output field size mimetype string type of the resource properties object output field properties content string response content thumbnail string output field thumbnail output example {"status code" 200,"response headers" {"content type" "application/json;charset=utf 8","transfer encoding" "chunked","connection" "keep alive","date" "wed, 15 oct 2025 09 36 20 gmt","server" "atlassianedge","timing allow origin" " ","x arequestid" "4721db0c6b91ec8c05ff58ae054477b8","set cookie" "atlassian xsrf token=755c33fb6d023b29c1756351184ee8bdac229bf7 lin; path=/; sames ","x aaccountid" "712020%3aab4557ae 85d6 46c8 a771 c72866daee0d","cache control" "no cache, no store, no transform","x b get comments retrieves all comments associated with a specified issue in atlassian jira using the issueidorkey endpoint url /rest/api/2/issue/{{issueidorkey}}/comment method get input argument name type required description parameters startat number optional the page offset, if not specified then defaults to 0 parameters maxresults number optional how many results on the page should be included defaults to 50 parameters orderby string optional ordering of the results parameters expand string optional optional flags renderedbody (provides body rendered in html) path parameters issueidorkey string required the id or key of the issue to get comments for input example {"parameters" {"startat" 0,"maxresults" 1,"orderby" "created","expand" "renderedbody"},"path parameters" {"issueidorkey" "scrum 1"}} output parameter type description status code number http status code of the response reason string response reason phrase startat number output field startat maxresults number result of the operation total number output field total comments array output field comments comments self string output field comments self comments id string unique identifier comments author object output field comments author comments author self string output field comments author self comments author accountid string unique identifier comments author emailaddress string output field comments author emailaddress comments author avatarurls object url endpoint for the request comments author avatarurls 48x48 string url endpoint for the request comments author avatarurls 24x24 string url endpoint for the request comments author avatarurls 16x16 string url endpoint for the request comments author avatarurls 32x32 string url endpoint for the request comments author displayname string name of the resource comments author active boolean output field comments author active comments author timezone string output field comments author timezone comments author accounttype string type of the resource comments body string request body data comments updateauthor object output field comments updateauthor comments updateauthor self string output field comments updateauthor self comments updateauthor accountid string unique identifier output example {"status code" 200,"response headers" {"content type" "application/json;charset=utf 8","transfer encoding" "chunked","connection" "keep alive","date" "wed, 15 oct 2025 09 40 35 gmt","server" "atlassianedge","timing allow origin" " ","x arequestid" "3cf3be5bed36ce8852b022b22fad4680","set cookie" "atlassian xsrf token=34825ff539cae4c90e5c4d95ea5046864837e5a9 lin; path=/; sames ","x aaccountid" "712020%3aab4557ae 85d6 46c8 a771 c72866daee0d","cache control" "no cache, no store, no transform","x b get issue retrieve a full representation of a jira issue using the specified issue key or id endpoint url /rest/api/2/issue/{{issueidorkey}} method get input argument name type required description path parameters issueidorkey string required parameters for the get issue action parameters fields string optional the list of fields to return for the issue by default, all fields are returned parameters expand string optional parameters for the get issue action parameters properties string optional the list of properties to return for the issue by default no properties are returned parameters updatehistory boolean optional parameters for the get issue action input example {"parameters" {"fields" "fields","expand" "expand","properties" "properties","updatehistory"\ false},"path parameters" {"issueidorkey" "10002"}} output parameter type description status code number http status code of the response reason string response reason phrase expand string output field expand id string unique identifier self string output field self key string output field key fields object output field fields fields watcher object output field fields watcher fields attachment array output field fields attachment fields sub tasks array output field fields sub tasks fields description string output field fields description fields project object output field fields project fields comment array output field fields comment fields issuelinks array output field fields issuelinks fields worklog array output field fields worklog fields updated number output field fields updated fields timetracking object output field fields timetracking names object name of the resource schema object output field schema output example {"status code" 200,"reason" "ok","response headers" {},"json body" {"expand" "renderedfields,names,schema,operations,editmeta,changelog,versionedrepresentatio ","id" "10002","self" "http //www example com/jira/rest/api/2/issue/10002","key" "ex 1","fields" {"watcher" {},"attachment" \[],"sub tasks" \[],"description" "example bug report","project" {},"comment" \[],"issuelinks" \[],"worklog" \[],"updated" 1,"timetracking" {}},"names" {},"schema" {}}} get issue transitions retrieve available workflow transitions for a specified issue in atlassian jira using the issueidorkey endpoint url /rest/api/2/issue/{{issueidorkey}}/transitions method get input argument name type required description path parameters issueidorkey string required parameters for the get issue transitions action parameters transitionid string optional parameters for the get issue transitions action parameters expand string optional parameters for the get issue transitions action input example {"parameters" {"transitionid" "145","expand" "transitions fields"},"path parameters" {"issueidorkey" "abc 123456"}} output parameter type description status code number http status code of the response reason string response reason phrase expand string output field expand transitions array output field transitions transitions id string unique identifier transitions name string name of the resource transitions to object output field transitions to transitions to self string output field transitions to self transitions to description string output field transitions to description transitions to iconurl string url endpoint for the request transitions to name string name of the resource transitions to id string unique identifier transitions to statuscategory object status value transitions to statuscategory self string status value transitions to statuscategory id number unique identifier transitions to statuscategory key string status value transitions to statuscategory colorname string name of the resource transitions to statuscategory name string name of the resource transitions hasscreen boolean output field transitions hasscreen transitions isglobal boolean output field transitions isglobal transitions isinitial boolean output field transitions isinitial transitions isavailable boolean output field transitions isavailable transitions isconditional boolean output field transitions isconditional transitions islooped boolean output field transitions islooped output example {"status code" 200,"response headers" {"date" "thu, 14 mar 2024 10 55 21 gmt","content type" "application/json;charset=utf 8","server" "atlassianedge","timing allow origin" " ","x arequestid" "01a9bcce2d2e22ac682648d57a91d21c","set cookie" "atlassian xsrf token=ae9ec298fd6a6260aad919dc8100fbac03038d54 lin; path=/; sames ","x aaccountid" "63b4c0c5082abdd71bb64f24","cache control" "no cache, no store, no transform","vary" "accept encoding","content encoding" "gzip","x content type options" "nosn get issuetypes retrieve all issue types available in atlassian jira on premise that the current user has visibility of endpoint url /rest/api/2/issuetype method get output parameter type description status code number http status code of the response reason string response reason phrase output example {"status code" 200,"response headers" {"content type" "application/json;charset=utf 8","transfer encoding" "chunked","connection" "keep alive","date" "wed, 15 oct 2025 09 51 23 gmt","server" "atlassianedge","timing allow origin" " ","x arequestid" "98aec3331636c732add6a1589479d7cd","set cookie" "atlassian xsrf token=2d037883c1d7293963032df25cc910d647853d18 lin; path=/; sames ","x aaccountid" "712020%3aab4557ae 85d6 46c8 a771 c72866daee0d","cache control" "no cache, no store, no transform","x b issue transition performs a transition on a jira issue using the specified issueidorkey and updates or sets fields as needed endpoint url /rest/api/2/issue/{{issueidorkey}}/transitions method post input argument name type required description path parameters issueidorkey string required parameters for the issue transition action transition object optional parameter for issue transition transition id string optional unique identifier transition name string optional name of the resource transition to object optional parameter for issue transition transition to name string optional name of the resource transition to id string optional unique identifier transition to statuscategory object optional status value transition to statuscategory id number optional unique identifier transition hasscreen boolean optional parameter for issue transition transition isglobal boolean optional parameter for issue transition transition isinitial boolean optional parameter for issue transition transition isavailable boolean optional parameter for issue transition transition isconditional boolean optional parameter for issue transition transition islooped boolean optional parameter for issue transition update object optional date value fields object optional parameter for issue transition input example {"json body" {"transition" {"id" "171","name" "send to backlog","to" {"name" "backlog","id" "10103","statuscategory" {"id" 2}},"hasscreen"\ false,"isglobal"\ false,"isinitial"\ false,"isavailable"\ true,"isconditional"\ false,"islooped"\ false},"update" {},"fields" {}},"path parameters" {"issueidorkey" "abc 123456"}} output parameter type description status code number http status code of the response reason string response reason phrase response text string output field response text output example {"status code" 204,"response headers" {"date" "thu, 14 mar 2024 11 46 30 gmt","content type" "text/html;charset=utf 8","server" "atlassianedge","timing allow origin" " ","x arequestid" "c3e33947c9397314e2813e89af530487","set cookie" "atlassian xsrf token=8080b8cf421caf2bc881add5736b334bbe88b6a2 lin; path=/; sames ","x aaccountid" "63b4c0c5082abdd71bb64f24","cache control" "no cache, no store, no transform","x frame options" "sameorigin","vary" "accept encoding","x content type options" "nosnif search executes a search for issues in atlassian jira on premise using the jira query language (jql) endpoint url /rest/api/2/search method get input argument name type required description parameters jql string optional parameters for the search action parameters startat number optional parameters for the search action parameters maxresults number optional parameters for the search action parameters validatequery boolean optional parameters for the search action parameters fields string optional parameters for the search action parameters expand string optional parameters for the search action input example {"parameters" {"jql" "jql","startat" 0,"maxresults" 100,"validatequery"\ true,"fields" "fields","expand" "expand"}} output parameter type description status code number http status code of the response reason string response reason phrase id string unique identifier title string output field title type string type of the resource properties object output field properties properties expand object output field properties expand properties startat object output field properties startat properties maxresults object result of the operation properties total object output field properties total properties issues object output field properties issues properties warningmessages object response message properties names object name of the resource properties schema object output field properties schema definitions object output field definitions definitions field meta object output field definitions field meta definitions history metadata participant object response data definitions json type object type of the resource definitions link group object output field definitions link group definitions simple link object output field definitions simple link additionalproperties boolean output field additionalproperties output example {"status code" 200,"reason" "ok","response headers" {},"json body" {"id" "https //docs atlassian com/jira/rest/schema/search results#","title" "search results","type" "object","properties" {"expand" {},"startat" {},"maxresults" {},"total" {},"issues" {},"warningmessages" {},"names" {},"schema" {}},"definitions" {"field meta" {},"history metadata participant" {},"json type" {},"link group" {},"simple link" {}},"additionalproperties"\ false}} response headers header description example atl request id http response header atl request id 7fc20497 6a2a 492b a6f1 00b52f62e9f9 atl traceid http response header atl traceid 2fa0df8fffa74b83b184fdbf66605aa7 cache control directives for caching mechanisms no cache, no store, no transform connection http response header connection keep alive content encoding http response header content encoding gzip content type the media type of the resource application/json;charset=utf 8 date the date and time at which the message was originated thu, 01 jan 2024 00 00 00 gmt nel http response header nel {"failure fraction" 0 001, "include subdomains" true, "max age" 600, "report to" "endpoint 1"} report to http response header report to {"endpoints" \[{"url" " https //dz8aopenkvv6s cloudfront net "}], "group" "endpoint 1", "include subdomains" true, "max age" 600} server information about the software used by the origin server atlassianedge server timing http response header server timing cdn upstream layer;desc="edge",cdn upstream dns;dur=0,cdn upstream connect;dur=1,cdn upstream fbl;dur=321,atl edge;dur=315,atl edge internal;dur=16,atl edge upstream;dur=299,atl edge pop;desc="aws ap south 1",cdn cache miss,cdn pop;desc="bom78 p1",cdn rid;desc="tupgfefdcjui2tmorr6h6amqlwsq70xsaiq5prjlbs45pdftsybt8g==",cdn downstream fbl;dur=325 set cookie http response header set cookie atlassian xsrf token=2d037883c1d7293963032df25cc910d647853d18 lin; path=/; samesite=none; secure strict transport security http response header strict transport security max age=63072000; includesubdomains; preload timing allow origin http response header timing allow origin transfer encoding http response header transfer encoding chunked vary http response header vary accept encoding via http response header via 1 1 5b3ba25f8eac620d91408a458d7b2a9e cloudfront net (cloudfront) x aaccountid http response header x aaccountid 712020%3aab4557ae 85d6 46c8 a771 c72866daee0d x amz cf id http response header x amz cf id 873qitodnk1fmk0h9evrsyjnpefn2cuw0alogi0snn0hdeguve3asq== x amz cf pop http response header x amz cf pop bom78 p1 x arequestid http response header x arequestid 3cf3be5bed36ce8852b022b22fad4680 x beta ratelimit limit http response header x beta ratelimit limit 350 x beta ratelimit remaining http response header x beta ratelimit remaining 348 x cache http response header x cache miss from cloudfront x content type options http response header x content type options nosniff x frame options http response header x frame options sameorigin x xss protection http response header x xss protection 1; mode=block