marc -Collabello--Phase Locked- Community Champion

You can't just put a reverse proxy before Jira. This won't work. However you can proxy API requests through a proxy. For this to work, you'd need to sort out an authentication method for the proxy. One possibility might be Basic Auth: https://developer.atlassian.com/cloud/jira/platform/basic-auth-for-rest-apis/

Agree, Jira Cloud is quite slow.

Hi @ricardo.carvalho.glo , I don't believe this is possible with Confluence Automation.

As far as I know Atlassian has not committed to building this.

It seems Atlassian has changed the caching when using the Page Properties macro. Sometimes it helps to do a full page reload, i.e. pressing the F5 button.

Obviously adding Vanta is an additional security risk. However maybe Vanta catches other security risks and implements required audit controls. This might be a net positive.

With a new version I meant: when atlassian-connect.json changes, this counts as a new version of the addon.

One thing you can check: After setting up staging with a new version, have you done a new install (i.e. uninstall and then install) on your staging instance? This is required to reload atlassian-connect.json into an instance.

Can you post a screenshot of the details of your automation? A 404 response could also mean that permissions are not ok.

Unfortunately Atlassian has decided that users must endure the popups. You can't disable them.

Unfortunately refreshing data is currently not supported in Confluence databases.

Hi @Min Wang , In order to help you, we'd need more information about your descriptor. The screenshots only show a single macro in the descriptor.

Hi @Patrick Geering , Indeed, you can use Confluence as a Document Control system. You can build the system yourself if you use Confluence Automation (when you use a Premium subscription). Probably you are also required to use an addon from a third party (we make Document Control for Confluence Cloud). Most likely you need…

I believe that is currently not possible.

One way to copy over the manual would be use a separate space with an unique name in both Confluence instances. This would allow you to write the manual in one instance, export the space and import it in the other Confluence instance. If you use any addons, make sure they are present in both instances.

If the customer "owns" the manual, I'd recommend that the customer creates a space in their Confluence and invites you. In that case the customer keeps a copy of the history of the document/manual.

* Just keep the rest of the information for now. * The "documented" link are the blue letters in your screenshot above. When you click on the blue "documented", you get more information.

Just try adding the smart value. As a first step, you can add it in the quotes after {{issue.key}} (i.e. {{issue.key}} / {{content.url}} ). Then you'd need to click on the "documented" link and add it to e.g. another custom field.

If i understand it correctly, you should modify the action "create Jira ticket" to include the smart value.

You would need to run your own proxy server and rewrite the URLs. This really depends on the proxy server you have, and what security rules you have.

There's a "create ticket in Jira" action, which can take the "{{content.url}}" smart value.

Currently Confluence databases don't support the re-import of data with an update of the original data.

Hi @Sherry Nightingale , One way to do this is to add a "smart value" to your Jira ticket creation rule in Confluence Automation. You could add the smart value `{{content.url}}`.

Hi @Mariem MOUKHLISSI , One solution to the problem could be to use a proxy server. The proxy can add the token to the requests, without exposing the token to the client. However this also has security implications.

Hi @Kristie White , Thank you for reporting this. The error is highly unusual. Can you contact us at support@phaselockedsoftware.com such that we can help you directly?

Technically you can do this by developing a Jira app in either the Connect or Forge platform: https://developer.atlassian.com/ However there's also the legal and data privacy aspect to consider.

Hi @Kristie White , Not sure what the issue with ScriptRunner is. As an alternative, we've built an addon which allows this without writing a script: Document Metadata for Confluence Cloud. This allows you to directly add page metadata like the page title, author, last editor, last edited date etc. into the page.

Hi @alexandru_ochiu , From what I understand, you can't modify the request access page.

Hi @Heide Behrens , We make a Confluence signature app, which will show the date of the approval/signature on the page. It's Document Control for Confluence Cloud, and free for up to 10 users (as you are on the free tier). The app also has page restrictions management, however I'm not entirely sure if that would fit your…

Hi @Satty , IF I understand your workflow correctly, you have a page level review cycle, and you need to notify someone when a review cycle is completed. In principle this can be implemented with Confluence Automations. Sometimes you would also need an addon, like our Document Control for Confluence Cloud. This addon…