Rilwan Ahmed Community Champion

Hi @Shirish 1. Go to project settings --> Components . Change the default assignee to unassigned from project lead for all the components 2. Go to Project settings --> User and Roles --> Edit "Edit Defaults" on the right top and select unassigned for "Default Assignee"

Hi @Alexander Ziegltrum , We cannot display "Creator" field in issue view. Already there is an suggestion request. You can vote and watch for the updates. https://jira.atlassian.com/browse/JRACLOUD-60281 Workaround: Create a single user custom field and add in required issue type screens. Create project automation as below…

Hi @Leo , The user should be part of Browse users Global permission. To modify, Go to admin settings --> system --> Global permissions (https://g<baseURL>/secure/admin/GlobalPermissions!default.jspa) Check what groups have Browse users permissions. You can modify the permission and add required groups into it. 

Hi @Teresa Ruiz-Rico Gómez I suggest, create different rules for daily and weekly scheduled jobs. It would be easy for you to identify and check the audit logs in future. 

Workaround: Add a JQL condition in Scheduled issues trigger i.e. Project = <Your Project> Create Component "FOR EACH: Create a Branch" --> Branch rule/ Related issues --> Send Email. 

Hi @Teresa Ruiz-Rico Gómez , As informed earlier, the rule is triggered before the ticket is being assigned. Even I was able to reproduce the issue. 

Hi @evans.keith82 , Welcome to the community !! This community is for Atlassian products related. What are you exactly looking for ?

Hi @Teresa Ruiz-Rico Gómez , 1. How is the ticket being assigned to specific users ? Is it by automation rule OR project default settings OR Components lead ? Seems rule is running before the ticket gets assigned to the Assignee.

Welcome to the community @carlos_ijalba !!

Hi @Teresa Ruiz-Rico Gómez , Is the ticket being auto-assigned to anyone as soon as it is created ? Or atleast before the rule is run ? 

Hi @Gunasekaran N , You cannot restrict users/customers to submit requests only between 8:00am and 4:30pm. Either you need to make your Jira down or remove permissions during these times. The JQLs used will work only for created ticket and it is not the right way to use in the workflow validator. Please note: The 'Date…

Hi @MJCorcoran , You have not set up any goal in your SLA. Please configure SLAs with the goal and conditions. Sample SLA screenshot: More details about SLA is in https://support.atlassian.com/jira-service-management-cloud/docs/create-service-level-agreements-slas/ 

Hi @rodrigo.monteiro , * If you are already a billing or technical contact, create a support ticket to Cloud technical support here. * If you are not yet a billing or technical contact, create a support ticket to the Customer Advocate support here.…

https://support.atlassian.com/jira-cloud-administration/docs/what-are-locked-custom-fields/

Hi @nhd nhd Welcome to the community !! There seems some conditions are not met to transition the ticket to "in coordination". May be some fields should be updated etc. Please contact your jira or project admin. They need to check the Workflow validators. 

Hi @Ebru A_ , Welcome to the community !! Please go through these documents to know how drafts work in Confluence https://confluence.atlassian.com/confkb/how-do-drafts-work-on-confluence-938043306.html https://confluence.atlassian.com/doc/drafts-149040.html 

Hi @Prem , Welcome to the community !! Have any questions/issues using the JSM, please write them in https://community.atlassian.com/. Community members will try to help/solve them . 

Hi @Rémy Marchal , You can make use of Bulk Change and update the issue security for the existing tickets. In case if you are not able to set issue security for tickets, then see the cause and workaround mentioned in https://confluence.atlassian.com/jirakb/unable-to-bulk-edit-security-level-397803924.html

Glad that it worked !! Please accept the answer. Users with similar issue will find it useful.

Hi @Peter Jacobs For comments issue, please check with Plugin vendor as suggested by @John Funk 

Hi @Mohammed Haneefa Farook Go to Project settings --> Fields. Copy the Field configuration scheme name Now go to admin settings --> Issues --> Field configuration schemes Goto each Field Configuration and see if this particular field is marked Required. If marked, click Optional against it. Sample screenshot:

Hi @Felicia Cazer , Add contents to table without Edit page is not possible. Workaround: * Use Inline Table Editing plugin * Use Scaffolding plugin Please note: Plugins will be paid ones. Search in https://marketplace.atlassian.com/search?hosting=cloud&product=confluence for other options/free ones.

Hi @Alvin , Welcome to the community !! At present, there is no way to change the project default filter. You can vote and watch for the suggestion ticket raised https://jira.atlassian.com/browse/JRACLOUD-71176 for the updated on this feature 

Hi @Arti Bagewadi You want to delete the project OR delete a attachment in the ticket ? If you have required permissions to delete attachment, then just hover the mouse over the attachment, you will see delete icon. To delete all attachments in a ticket, then click on 3 dots near attachment and click "Delete All" ?

Hi @Claire Jamieson , Please check if the required access was granted on source confluence space for the required users before the migration. If access was restricted in source, same will be applied to migrated space. Please note: Permissions and restrictions aren't customizable on the free plan.

Hi @Mohammed Haneefa Farook , Seems the field in required field in screen context. Go to project settings --> Screen. See if the field is marked required. Now remove the field from create screen and come back to request type and remove here as well. 

Hi @Anna Kovalchuk , Welcome to the community !! My personal opinion: Atlassian in their support pages use scroll view port. I feel it is pretty good if you want your confluence to look like a help Centre with navigations. Sample…

Hi @Peter Jacobs , {{issue.key}} will only send the ticket key without the url. Please recheck your automation rule. I have attached screenshot from my rule and email. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

Hi @Roland Uittenbogaard , You can hide the request type. This will not show for users in customer portal. Service desk team will be able to update to this option from jira view whenever required. Steps to hide request type: * Go to project settings --> Request type * Click action menu (3 dots) against required request…

Hi @Zein Saaeda , As per the link shared above, All members of your team have the same permissions, so any member of the team can invite new team members or remove other team members. Can you share the screenshot of the page ?