Thomas Deiler_db00h3 Community Champion

Dear @[deleted] , I recommend to open a support request at Atlassian. So long Thomas

Dear @Wang ZY , I tried to reproduce what you described. With Confluence 6.15.6. all curl commands worked as expected. Regardless if taking an admin or non-admin account. Have you already tried with a REST client? So long Thomas

Dear @Elijah Scherz , have you tried to paste the whole JSON request inside postman or any other REST client? Does the same error occur? So long Thomas

Dear @Abhinav Arae , you can do this in two different manners: Option 1: Read this article and adapt server.xml to your needs. Option 2: Block the URL in front of Tomcat - within the reverse proxy configuration. For nginx follow this article. So long Thomas

Dear @[deleted] , you seem to be quite new with Atlassian tools, so I recommend to search the marketplace. You can get for all plugins evaluation licenses for free. So you can take your time to check out which plugin fullfills your requirement. So long Thomas

Dear @Jeremy Price , I think not possible out-of-the box. But If you have a list of user logins you could do with small script from outside via REST API: https://docs.atlassian.com/atlassian-confluence/REST/6.6.0/#user/watch-addContentWatcher Let me know if this could work for you - I can assist in scripting. So long Thomas

Dear @Nathan Randell , you can do from outside Jira with the API: https://docs.atlassian.com/software/jira/docs/api/REST/8.1.2/#api/2/auditing Write a cron job that pulls this information. It will be exported in JSON format. Eventually you have to convert this data, depending on the interface of your Security Event…

Dear @Denis , in the security advisory it is written: Customers who have upgraded Jira Server & Jira Data Center to versions 7.6.14, 7.13.5, 8.0.3, 8.1.2, or 8.2.3 are not affected. So you can do what you decided. So long Thomas

Dear @Owen Jones in most cases AD connection to Confluence are read-only. Means, creating users in Confluence will not populate them to AD. Create the user in AD. Then he will show up. I have in mind, that Atlassian announced in the past a new feature to exactly do what you wanted. But I am unsure if this was for…

Dear @Rik Vanmechelen , the action "move to board" depends on how you mapped the statuses of your issues to the board columns. If the origin status is mapped to a different column than the target status, then the issue will (visually) move. The second question: Yes you can do. Therefore you have to alter the issues…

Dear @Christian Laguerre , best you contact the Atlassian support. The community (mostly non-Atlassian volunteers) has no access to information bound to your Atlassian account. So long Thomas

Dear @Gabriel Sandoval , your issue seems to be related to CONFSERVER-55339. Anyhow, it seems that Atlassian simply didn't implement your requirement (in the Jira Macro), yet. So long Thomas

Dear @joker yang , if you would like the community to help you with your problem, I strongly recommend to post more information than 19 words and a screen shot in Chinese. So long Thomas

Dear @Rajesh Ramankutty , have a look at those articles: Set default comment visibility restrict comment visibility to team But be aware of this: JRASERVER-43747 If this doesn't help you can check this plugin. So long Thomas

Dear @Kamil Beer , this sound like the mapping got lost. Probably too late for you, but for other readers: Never do such critical operations on production environments without verifying first on a staging environment. So how this with the user works. Following case: * Jira is attached to AD. (LDAP) * users are assigned to…

Dear @Jiri Pik , eventually this is a known bug. Please have a look at CONFSERVER-55419. Fell free to vote for it. If it is different, contact the support to verify. So long Thomas

Dear @Rahul_Purohit , there was a typo - I fixed in my answer: False: https://<comapny-domain>/rest/content/<page-id>/child/attachment True: https://<comapny-domain>/rest/api/content/<page-id>/child/attachment So long Thomas

Dear @Brandon Miller and @zzw8200465323 , can you please post the JSON dump that is sent to Jira, that is causing the problems? So long Thomas

Dear @Sam Ferguson , you are right. It is written here. Just the comment. So long Thomas

@Siqing Li , nice to hear that you were successful. Please accept this answer, when you think this can help others, too. So long Thomas

@Niyi Odumosu , your questions isn't directly related to this article. Anyway, OAuth is not mandatory when you access your own Jira Server. User/Password works, too. For accessing Jira Cloud, you will require OAuth. So long Thomas

For a more recent version of this article follow this link.

Dear @Amy Lee , I would implement it with webhooks and the REST API. * Add a Webhook Listener to the workflow for the approved status * create a script, called by the webhook, on a server that creates the new project by the REST API (POST /rest/api/2/project). So long Thomas

Dear @Daniel Wendler , this how Jira is designed. Either you * (not recommended) shut down jira and alter the data via SQL * you export your project to XML (dump) modify the data and re-import overwriting the old information. So long Thomas

Dear @Andrew Chung , this is a built-in functionality. As Admin, goto "User Management" and click on "invite users" button. So long Thomas

Dear @Hayley Young , your requirement is not that easy to fulfill. Basically this would require a compare of two JQL queries, which is done inside the gadget. The gadgets compare functionality is not available outside itself. So you will need a (commercial) plugin that reports this automatically. Of cause you can do this…

Dear @Hera Macris , unfortunately there is no functionality to only hide the backlog. Either a user can see a kanban board and its issues or not. But you can restrict moving the issues by drag and drop and working on a board by remove the permissions: * Schedule Issues * Manage Sprints * Edit Issues So long Thomas

Dear @Nur Iza Khairulnisaq , can you post the exact message why it is insecure? date - host - CA authority ... So long Thomas

Dear @Mina A , have a look at this post. So long Thomas

Dear @Mina A , I don't know your piece of software but I know the REST API. You have to * set the custom header "X-Atlassian-Token" "nocheck" * you have to wrap the attachment as a multi part entity * The name of the binary body has to be "file" So long Thomas