Comments
-
You can't connect SQL server to Jira cloud. There's no user accessible SQL database.
-
Hi @Mark Gillespie , Probably this user has indeed created a new Confluence instance. Atlassian considers users "their Atlassian users" and not your orgs users. So all users can create new instances. Sometimes this happens by non technical users without realizing the implications. What you see is part of the newer controls…
-
Hi @Juba Aouragh , You could put the page into a separate space, with edit rights for the project members. After this you can use the include macro to include the page in the 2 other spaces.
-
I don't know of a public timeline for this feature.
-
Hi @Stephan Jüstel , There's currently no way of getting the database contents by API.
-
yes. It's simplest to just test the API route in your browser when you are logged into Confluence, as the authentication cookies are already set up.
-
Hi @Caroline Dumouchel-Hudon , My recommendation is to contact Atlassian support directly. It can be difficult to sort out macro issues on public pages.
-
Each account must have an email address, unfortunately.
-
You could use an external service like https://craftmypdf.com/pdf-generation-api/ (no affiliation, not vetted).
-
It would help if you showed on the page who is behind the app, what the terms of use and privacy policy are. Also I'm wondering if the use of "Jira" in the domain is ok with Atlassian and their branding guidelines.
-
Hi @AnukrityJain , my recommendation is to contact the support of the 'html-bobswift' macro.
-
Hi @Liza Wu , The error code 404 is not defined for the APIV2 pages endpoint. I'd recommend to ask this question here: https://community.developer.atlassian.com/
-
Hi @Lalithesh , There is no direct workaround in Jira vailable. One option might be to send the data through a web request to an external system to do the PDF conversion.
-
Hi @Eric Zakariasson , jirawrapped asks for quite some permissions from users. I would not put in my Atlassian credentials in such a site.
-
Sometimes these errors are caused by temporary issues. Just try again later.
-
It seems the reporter id is not valid?
-
Correct, after import you can't change it anymore.
-
Hi @ITAM SAM , IF you are a normal user in Confluence, you have permission to access the site. The permission is implicit in being a normal user, and so is not listed in the portal.
-
Yes, it is possible. However changing the exported files can be complicated.
-
Hi @Christoph Pieper , From within Confluence, you can't change the old user. However before importing, you could change the import files from the old user to the new user. Changing these files is a bit like programming.
-
Hi @Kristian Klima , Indeed, the use case is somewhat different than Databases. However I believe it is what @Isabella L_ wants to achieve. Unfortunately Confluence does not support it natively, and the only way seems to be the approach we take with Document Metadata.
-
Hi @Kristian Klima , This works by adding the content status to the content property macro. You can get more information by following the support link to https://www.phaselockedsoftware.com/en/document-metadata/documentation/#content-status You can also contact our support through…
-
Hi @Isabella L_ , This is not directly supported in Confluence. However we make an addon which allows you to use the page status in a page properties report: Document Metadata for Confluence Cloud You can see documentation here: https://www.phaselockedsoftware.com/en/document-metadata/documentation/#content-status Feel…
-
Hi @André Cusson , In cases like this, it often helps to contact Atlassian support directly and request a reindex of Confluence.
-
Hi @Alicja Mostowik , Unfortunately it is currently not possible to copy/move tasks between databases.
-
Hi @Barbara Acker , Out of the box, Confluence Cloud does not support approval of Documents. However you can build a QMS using Confluence and some addons. Some of our customers use Document Control for Confluence Cloud to build and sustain their QMS (paid addon). Hope this helps.
-
A proxy won't work. I think the main reason is the TLS termination and the communication with multiple Atlassian domains.
-
Custom domains do not work with proxies. You need to change your DNS records as instructed by Atlassian. Once the DNS records have propagated, you can use Jira with your custom domain.
-
Basically you can't use Jira Cloud behind a reverse proxy.
-
You need to export and backup the data yourself, Atlassian won't do this for you.