Thomas Deiler_db00h3 Community Champion

Dear @Camille Lecerf , please have a look at this issue. If this will not help at all, raise a request at Atlassian support. So long Thomas

Dear @Ryan O'Donnell , basic auth is deprecated - use api tokens instead. So long Thomas

Dear @Anton Maleev Especially in software development it is completely unrealistic to put two developers on the same task. This is not the whole truth: https://en.wikipedia.org/wiki/Pair_programming So long Thomas

Dear @Aaron Jones , it is pretty simple. Following this document, you just have to replace the password value with the token value. But be sure to use the email as user name. So long Thomas

Dear @Alexandra Wiechers , unfortunately you have to wait for this feature (JSDSERVER-2303). But you can vote for it. So long Thomas

Dear @[deleted] , I have read your post twice to figure out what you plan to do with this XML - I failed. Can you please tell us what you wanna do with this XML and where/when this exception is thrown? So long Thomas

Dear @[deleted] , this sound like an issue with the DB. Have you tried to cross link them? Just switch the DB between both instances and see if the error switches, too. So long Thomas

Dear @Ayoub Karaa , then you have to parse the JSON data on your own. There will be for sure a lib that will assist, but you will need to understand the JSON structure. Best you have a closer look to Cloud REST API. For detailed coding question, best you ask the developer…

Dear @Virginia Elliff , this seems to be a know problem: JRACLOUD-65579 You simply cannot (yet) do what you want. So long Thomas

Dear Samira, most probably this is a SSL cert issue. Jira connects to itself via Rest API. When the SSL cert is selfsigned it has to be added to the Java keystore to be recognized. So long Thomas 

Matthew, seems you know what you do - to open that request at Riada is best. Btw, which Insight version do you use?

Dear @Matthew , have you changed the GC as recommended by Riada? So long Thomas

Dear @suruchi ablish first of all - an end of life warning is not too serious. When the 49 days are over, your Confluence will continue to work. Atlassian will just not support it anymore. Have a look at the upgrade matrix. The release and upgrade note will tell you when you have to walk a specific upgrade path. I…

Dear @Yann MITCHOZOUNOU , Of which type are both custom fields with ID 13034 and 10409? Have you tried to paste the json request data, created by your code, in a REST client to verify? So long Thomas

Dear @Dev unfortunately I have not the solution for your requirements. But anyhow "Remaining Time" and "Epic/Story" doesn't really fit. They should be ideally relatively estimated. With the team velocity known and portfolio you can make that what you want visible: On the overview of portfolio you will see then the…

Dear @Роман Вегелин , you have to parse the history. For +1000 issues i recommend the REST API: * JQL for your issues (expand=changelog) (GET /rest/api/2/search) * for each issue look for history entries within a specific date range * update issue by replacing the "to" values with the "from" values (PUT…

Dear @Virginia Elliff , to be honest, I think this is default behavior of the REST. Just fire two requests short after creating news users: DELETE /rest/api/2/group/user?username=newuser&grouname=jira-software-users POST /rest/api/2/group/user?groupname=newgroup {"name": "newuser"} so long Thomas

Dear @Samira Spago , I strongly recommend the use of a reverse proxy (Apache,nginx, ...) that terminates SSL instead of enabling this in Tomcat. If you running on Linux you can follow my article how to set up with nginx. This is best practice and also recommended by Atlassian. So long Thomas

Dear @Jannick Hald , this kb article could help. So long Thomas

Dear @David Vu , the REST path seems to be fine. Assuming "KEY-666" really exists and the user has the permission to view. Is it possible, that your Jira server has a different context? instead of https://jira.corp.birchstreet.net https://jira.corp.birchstreet.net/jira ??? So long Thomas

Ok. You didn't say that you also have Jira. Next time please provide as many information as possible.

Dear @SHIP Support , have a look at this article and the HTTP location reference. So long Thomas

Dear @akota , if this is not a temporary issue, you can fetch the user information with ​ GET /rest/api/2/user?username=tgiorshev Otherwise have a look at https://status.atlassian.com/ to see if there is an incident. So long Thomas

Dear @Susana Samaniego see CONFSERVER-55307. At all there does not even exist a suggestion for Oracle 19c. Feel free to open a new and vote for it. So long Thomas

Dear @[deleted] , please open a support request at https://support.atlassian.com/contact/#/ So long Thomas

Dear @Ayoub Karaa , so you already get JSON responses with your spring boot? So long Thomas

Dear @Geralt yes, this is possible, but poor admin, who has to accept all those issues. Normally this is done by the Product Owner. I recommend to allow anybody to add items to the backlog - important - at its very end (bottom). The PO is the one who will decide if an item will make it inside a sprint or not. So technical…

Dear @Milan Chheda [INFOSYSTA] , yes you can do - the XML dump is DB vendor independent. I assume that you know this article already. Normally the DB import can happen without plugins already installed. Jira will import them, too. Also note that there is an issue with all 8.2.x versions. So I recommend to wait for a fixed…

Dear @Alex Oreshkin , I assume following, due to lack of information: * you have copied the confluence.cfg.xml to confluence-home * you adapted this file to fit to the new DB * you configured the confluence-home path * you have the right JDBC drivers for your Confluence/MSSQL version at place * firewalls do not block any…

Dear @Gabriely Gavanski , to know what's going on on Cloud, have a look at https://jira-service-desk.status.atlassian.com/. If your observation differs, contact the support. So long Thomas