Manoj Kumar Gangwar Community Champion

Hi @Xaxiry González Welcome to the community! I would suggest you to raise a request with atlassian vendor using the below link. https://support.atlassian.com/

Hi @Nikola Perisic, I tried to load multiple pages in different spaces in two instances but got no error.

Hi @Dirk Ronsmans, You're right that Jira does not natively support creating a dynamic JQL query that directly retrieves all issues created by members of the same groups as the current user (while excluding the default access group). As a workaround, you may try something like below: creator in (membersOf("group1") OR…

Hi @HJ Yoon Unfortunately, there is no way. You need to manually create it in production. 

Hi @Teri Yeargin Welcome to the Atlassian community!! If you want an report based on assignment group change then you need to use the jql like below: "Assignment group" Changed after -1w Or you can change it as per your requirements. If you want based on assignee then follow the instructions suggested by @Harshit Grover

Hi @Nikki Hailey you can apply the page level restrictions. https://support.atlassian.com/confluence-cloud/docs/add-or-remove-page-restrictions/

Hi @Andrea Active sprints are only available on Scrum boards. Could you please share the board screenshot?

There is no error in the audit logs. Please check if the approver field is added on the Issue view screen as @Marc -Devoteam- said.

Hi @Francesc Juventeny, the Automation rule looks good. Could you please share a screenshot of the audit logs to check the issue?

Hi @Raymart Cruz There could be 1 or more reasons for this error. 1- Please check if the rule actor has sufficient permission to make the transitions. 2- Check the workflow if there is any validator or condition applied. 3- Check if the transition is available from Approved to waiting for approval.

* Yes, if automation is running many times and a particular issues doesn't have change reason field in that case it will show this error. 

Hi @mohanbabu.s Currently, I don't think such kind of apps are available for free.

Hi @Muhammad Ali Khan You can use a user permission validator in the workflow on Issue Creation then you can restrict issue creation based on the project role. Create a new role in the project and assign the role to the particular user.

Hi @Anders Wang Welcome to the community! It could be due to the recent Incident but it is resolved. You can raise a concern with Atlassian using the below link- https://support.atlassian.com/contact/ 

Hi @Gloria Jazdan I see that you are looking for a way to retrieve user information ( Department) using automation. In this case, referencing our documentation the smart value to retrieve user information does not provide such information: Automation smart values - users The following properties are accessible for all user…

Hi @jira-sales , Virtual service agents are currently only available with Jira Service Management

Hi @Jin, Yuehan Please reach out to the Confluence admins to grant to the ownership of the page again.

@Arnau Barbecho Barrado you are right. Currently, you can use only one trigger in the automation. To achieve this, you need to create two automation rules. 

Hi @Arnau Barbecho Barrado You can use the manual trigger so that agent can trigger the automation by clicking on the action button on the issue.

You can remove them by using the remove option then it will not be visible.

@Marc -Devoteam- totally agreed with you. 

Hi @Soundarya Saravanan Welcome to the community! You can create automation like the below: Trigger: when Comment added Condition: If Issue Type = Subtask Branch: For Parent Action: add comment Inside comment use the below expressions: {{comment.author.displayName}}: {{comment.body}}

Hi @Jens Prokoph You can define the fields under Project setting> Management> Request Type> Click on the specific request type and click on Issue view> the field which you want to show under more, click on three dots and hide when empty.

Yes, you can remove the confluence-user group from the space access setting and only users who are added individually to your space can access it.

Hi @Edgar Pusklevic You can check the space access setting and check which users & groups can access your space. If confluence-users group access is granted, other users can access your space and page if no page-level restrictions are applied.…

Hi @Aleena Welcome to the community! It is happening because the Resolution field is already set and has not been cleared after moving the ticket back to the open. To fix this, you can create an automation rule or add a post function on the workflow when the ticket is moved from closed to open then clear the resolution.…

Hi @Kathryn Kerr if you are getting 400 bad request then please raise a ticket with atlassian vendor. https://support.atlassian.com/ For some automation rule, we are also getting the 400 error so atlassian is investigating on it. 

Hi @PR23 I think it's not feasible. In Confluence, the requirement to enter a password when logging in is a site-wide setting and cannot be disabled selectively for space admins within individual spaces. Confluence doesn’t support the option to bypass login security or password requirements on a per-space basis, even if…

Hi @Michael Winters Welcome to the community! Please follow the below steps: Export (back up) multiple pages to XML If you want to export a space as an XML, Confluence can create a zipped archive of the XML. XML space exports can be used to import your space content into another Confluence space running the same or newer…

Hi @Lager , Welcome to the community! In Confluence Cloud, macros do not automatically apply headers and footers across all pages in a space. However, here are a couple of approaches that can help: * Template-Based Solution: You can create a page template that includes the header and footer content as reusable elements.…