Thomas Deiler_db00h3 Community Champion

Dear @Jason Harwood, I found two issues that could be related to your problem: JRASERVER-68412 JRASERVER-62668 Can you please verify? So long Thomas

Dear @Rainer Rauschenberg, beside setting the header "accept", "application/json" try to set additionally the following header "Origin", "https://<FQDN of your Confluence server>" You can read more details following this article. So long Thomas

Dear @Madhu Mullangi, have a look at this page. So long Thomas

Dear @Fabio Banfi, what will your benefit be with this linking? Just for better understanding. So long Thomas 

Dear @Jo-André Lia, please post your question again on https://community.developer.atlassian.com/ Thanks for understanding Thomas

Dear @Dominik, just to be sure, it's not a firewall issue. Have you tried telnet requestb.in 80 on command line of your Jira server? So long Thomas

Dear @Julien, please post your question again on https://community.developer.atlassian.com/ There you will get helped by the right community. Thanks for understanding Thomas

Dear @[deleted], have a look at: https://confluence.atlassian.com/upm/configuring-marketplace-connectivity-306350947.html You will need some additional servers to reach. So long Thomas

There already exists a suggestion. You can vote for this.

Dear @Bartlett, Leigh, you are right. I had a look in both Cloud and Server version. 60 min, 30 min and breach are the defaults. One solution would lead to a tool - breach. Trigger notifications less than 30 minutes by an external script that uses the REST API. Another way would be to raise a suggestion at…

To prevent password changing it can work by moving the guests to an external user directory (LDAP), that is for confluence just read-only. With the permission View you cannot comment. I doubt, that avatar modification and likes can be restricted.

Dear @Darren, with that many levels I recommend to evaluate the structure plugin. So long Thomas

Dear @Kanepetra, that just depends on your configuration. I recommend you create per space one group named eg. space1_guests, space2_guests, ... Then you globally allow users of this groups to log in. Per space you add one of this new groups just to the permission VIEW. That's it. You are done. So long Thomas

Dear @steven.southworth, Number of Users concurrently logged in This you can query with the Administration->System->User Sessions function Volume of E-mail Notifications You best enable Email logging or you grep your mail relay log file for counting Number of Concurrent Operations You mean DB operations? Then best with…

Dear @Kenneth Monge, that's the concept of the JSD license: You have to pay for agents. Otherwise everybody would buy Jira and just add JSD for $10. So long Thomas

Wonder if he already knows this page ...

Dear @Jean Pyronneau, Jira doesn't allow to delete users that are assigned at least to one issue. So the user must have been removed from another LDAP source. I remember a couple of years ago to fix this problem by creating a user with exactly the same username in Jiras internal User DB. Then these issues where 'claimed'…

Dear @ErnieErwee, two Atlassian products installed on the same server - there always rings a bell: Have you modified the session id of one of the products? On default it's named JSESSIONID for each tomcat installed. You can change this for Jira by modifying the file $JIRA_INSTALL/atlassian-jira/WEB-INF/web.xml If this…

The Request Type (internal Custom Request Type) is in a 1:1 relation with the issue type. In my JSD instance this field is visible but locked for any changes. So in the end there will not be any automation rule to do this job: changing Custom Request Type while keeping the Issue Type. So long Thomas

Dear @chandu valapala, your use case is quite "short" described. So I can just give one answer without realy knowing if this will solve your issue: Create a custom field named "Service Now Path" of type "text field single line" and fill this field when creating/modifying Jira issues with the REST API. So long Thomas

Dear @Martin Koisser, if I have understood your requirement correct, you would like to change the issue type while transitioning an issue. Can you give me a detailed explanation, why you would like to do this? Then I can probably help you more specific. So long Thomas

Dear @pkhera1, test cases are not part of Jira Software / Core. You need to buy this plugin (or alternatives). So long Thomas

Dear @Paul Brand, Jira replaces a resolution of NULL (resolution is EMPTY) with the word Unresolved. Of cause you can create a custom resolution named same, but it really does not make sense. So long Thomas

Dear @Paul Brand, I repeated your search queries. The first filter returned The value '"Unresolved"' does not exist for the field 'resolution'. Searching with either resolution = "Unresolved" or resolution = Unresolved returns the same amount of issues. Is it possible, that you Jira has a custom resolution named…

Have a look at this snippet: import org.apache.http.HttpEntity; import org.apache.http.entity.mime.HttpMultipartMode; import org.apache.http.entity.mime.MultipartEntityBuilder; import org.apache.http.Header; HttpPost postRequest = new HttpPost(url); postRequest.addHeader(/* has to be ""X-Atlassian-Token", "nocheck"" */);…

Dear @Kalyan, you have to create a MultiPartEntity request. Follow this https://developer.atlassian.com/cloud/confluence/rest/#api-content-id-child-attachment-post Have also a look at https://docs.atlassian.com/atlassian-confluence/REST/6.6.0/#content/{id}/child/attachment-createAttachments This is Confluence Server but…

Dear @Nate (이슬기) [Project Management] , I cannot recommend to directly access Jiras Database. Best you do this with the REST API. Aggregating the history information of an issue will let you track down the lead-time. But you will need some coding skills ... So long Thomas

Dear @Dominik Žarković, most probably your SSL certificate is not trusted by the JVM. To fix this you can do following: * create a new keystore including the public part of the cert of AD (with Oracles keytool) and add the following to the start scripts of Confluence* -Djavax.net.ssl.trustStore=/path/to/keystore * or add…

It seems not to be Jira that modifies the header. Has it worked once? Which change happened to the system that suddenly header and JSON data differ?

Ah! You a using Cloud?