Rilwan Ahmed Community Champion

Hi @alexej.friedrich , * Anyone with access to the service project can add request participants by including the participant’s email address in the “To” or “Cc” field when creating the request. * Depending on your JSM customer access settings and project's customer permissions, users will be able to add people to the…

* Idly Wada with sambar and chutney, Puttu * Hyderabadi Haleem * Malabar chicken/mutton biryani

Hi @rdi , Welcome to the community !! This could be the reason why the apps are blocked https://www.atlassian.com/blog/announcements/atlassian-stands-with-ukraine

Hi @raymond Scott , I could not find any links to give you the upgrade paths. Referring to the upgrade checklist, I think there should be no problem for upgrading from 8.2 to 9.12 https://confluence.atlassian.com/adminjiraserver0912/upgrade-checklist-1346046999.html I would suggest you to check these 1. Supported platforms…

Hi @raymond Scott , You can directly upgrade from confluence 7.13 to 8.5. No need of any intermediate versions. I would suggest, try upgrading in test server and then in production. Details in https://confluence.atlassian.com/conf85/confluence-upgrade-matrix-1283361508.html (at the bottom of the page)

Hi @Niklas Zarnecke , Go to admin settings --> Products --> Application links. From here you can create integration to separate wiki

Hi @Atlassian 29495 , As @Nic Brough -Adaptavist- suggested, go to Admin settings --> System --> General configuration and add enable Contact Administrators Form and add message Contact Administrators Message, so that users cone to know what needs to be done in case of dead end.…

Hi @Yaharin , Welcome to the community !! Go to your JSM project, in left navigation bar select boards. On top, you can see the share icon. 

Hi @Lukasz , From the screenshot you shared, it does not seems to be a team managed project. Instead it is a service management project (I can see SLA settings links). * Go to project settings --> Screens, check if the Approvers fields are in corresponding issue type screens. Mainly the Create Issue Screen * Go to Admin…

Hi @Adrien Riccardo , Welcome to the community !! Go to your project settings --> Request types. Click Edit fields for the required Request type and go to "Workflow statuses" tab. Here you can give any status name to show to the customer. There is no other way to show nay descriptions to the statuses

Open the config and see what is mentioned in "Issue reporter"

Hi @zoomr room , Welcome to the community !! LDAP logs are present in <confluence home>/logs/atlassian-confluence.log file.

Hi @Neha Thapak , Welcome to the community !! What is the error displayed ? As @Pramodh M suggested, check the fields required in jira project and the setup in Issue collector. Check if the Issue reporter has the permissions to create ticket Meantime, go through below link to troubleshoot the issue collector common issues.…

Hi @Quang Nguyen , If you are in jira cloud, use "FOR EACH: add a branch" component. This will run the rule for the sub-tasks created. More details is in https://support.atlassian.com/cloud-automation/docs/jira-automation-branches/

Yes. Please note: Product admin can also be Site admin/Organization admin. It all depends on the groups which user is added in. 

Hi @salim_testing , You can use workflow export and import functionalities. In Source jira * Go to admin settings --> Issues --> Workflow * Open required workflow. * Click export as xml or workflow as required In destination jira * Go to admin settings --> Issues --> Workflow * Click import (xml or workflow) and continue…

No, Only Project admins or Jira system admins can grant/revoke access

Hi @Azri Permissions work differently in Atlassian cloud compared to data center/server. In Atlassian cloud, there re different admin roles. * Product admins – They administer settings inside the product depending on group memberships (e.g. Jira and Confluence settings). Not all product admins need product access (e.g.…

@ribas , Remove yourself from the project roles. 

Hi @Lakshmi Kumari Go to your project settings --> Permissions --> Actions --> Edit permission * Remove "Service desk customer" role from all permissions * Instead Grant Browse Projects, Create Issues, Resolve Issues, Add Comments, Create Attachments and any other necessary permissions to "Service Project Customer - Portal…

Hi @ribas , You have 3 options * Archive project / Issues * Change permission scheme of projects. * Remove users from the groups/roles which grant the access to the project. 

Hi @[deleted] , Just remove "d". Use {{now.plusBusinessDays(30)}} More examples: https://support.atlassian.com/cloud-automation/docs/examples-of-using-smart-values-with-dates/

Hi @ribas , Welcome to the community !! Projects are displayed to the users based on their roles setup in permission scheme. To hide/close a project, I would suggest you to update the permission scheme attached to the project. i.e. Create a new permission scheme, add only required users/groups/role to browse project…

Hi @Deb Keene , Regardless of whether someone is a customer, agent, or admin, they will receive customer notifications if they: * Raise a request * Are added to the Reporter, Approver, or Request participant field on a request and have verified their email address * Belong to an organization that has allowed customers to…

Hi @Teresa Ruiz-Rico Gómez , Welcome to the community !! you need to update notification scheme and add the user field to the required actions. i.e. Go to project settings --> Notifications --> Actions --> Edit Notification. For required notification type (Example: Issue created etc.) --> Add -->User custom field -->…

Hi @Lakshmi Kumari , Is there any errors displayed while accessing the customer portal? Also please check the customer permission in your project. i.e. Project settings --> Customer permissions https://>baseURL>.atlassian.net/jira/servicedesk/projects/ITSM/settings/customer-permissions

Hi @Pankaj Rana , Run this SQL to get count of pages in trash. select count(CONTENTID) from CONTENT where CONTENT_STATUS = 'deleted' and CONTENTTYPE = 'PAGE'; Available CONTENTTYPEs are ATTACHMENT GLOBALDESCRIPTION USERINFO PAGE SPACEDESCRIPTION CUSTOM COMMENT BLOGPOST DRAFT Available CONTENT_STATUS are current deleted…

Hi @青山 明 , This feature is not available in Confluence cloud. There is already a suggestion ticket. You can watch and vote for it. https://jira.atlassian.com/browse/CONFCLOUD-4792

Hi @Vanessa Schreiber , Welcome to the community !! As you are in free plan, so you can't view and track changes made across your site in the audit logs. https://<baseURL>.atlassian.net/auditing/view If you are project admin, go to admin settings --> Issues --> Custom field. You can see list of all custom fields created by…

Hi @SPACE coders , jira.permission.edit.denied.group is same as jira.permission.edit.denied. It will block all users/groups/roles irrespective of them mentioned :( The other solution is to add only roles who needs the edit. i.e. jira.permission.edit.projectrole.1, Value = role ID first role who needs the access.…