Changing the Default Behavior and Content in Confluence
Customizing your Confluence Site
On this page
In this section
Related content
- IssueService validations does not run with provided user
- "Security level not valid for the current issue" error when creating issues in Jira Data Center
- "Security level not valid for the current issue" error when creating issues in Jira Data Center
- Can not create issue via REST API - Field 'xxx' cannot be set. It is not on the appropriate screen, or unknown, when using workflow property "jira.permission.createclone.denied"
- Unable to Create an Issue Through the Issue Collector Plugin due to Workflow's Validator
- When attempting to create an issue receiving an error message noting the issue can't be created right now.
- Jira Automation fails to transition an issue to destination status
- Unable to create issues due to unsupported content in Jira Server and Data Center
- Jira Login fails after userCache being flushed
- Jira server throws IssueNotFoundException when creating issues
Confluence comes with some handy default settings that determine what people see when they first enter the Confluence site, and the default content that is put into new spaces and other areas of Confluence.
Confluence administrators can change the settings to customize the behavior and the default content of their Confluence site:
Last modified on May 30, 2022
In this section
Related content
- IssueService validations does not run with provided user
- "Security level not valid for the current issue" error when creating issues in Jira Data Center
- "Security level not valid for the current issue" error when creating issues in Jira Data Center
- Can not create issue via REST API - Field 'xxx' cannot be set. It is not on the appropriate screen, or unknown, when using workflow property "jira.permission.createclone.denied"
- Unable to Create an Issue Through the Issue Collector Plugin due to Workflow's Validator
- When attempting to create an issue receiving an error message noting the issue can't be created right now.
- Jira Automation fails to transition an issue to destination status
- Unable to create issues due to unsupported content in Jira Server and Data Center
- Jira Login fails after userCache being flushed
- Jira server throws IssueNotFoundException when creating issues
Powered by Confluence and Scroll Viewport.