Summary

Currently if you are in Jira on site A and ask Rovo to create a Confluence page, it will create the page on Confluence for site A

Some organizations have Jira and Confluence on separate sites and would like to be able to configure Rovo to publish Confluence content to a different site

Example:

Jira exists on site A

Confluence exists on site B

User starts a chat with Rovo in Jira on site A and requests Rovo create a Confluence page on site B containing Jira work items from site A

Ideal behaviors:

• Ability to configure Rovo to publish Confluence content on a different site
• Ability to set a default Confluence site so all Rovo content is published there