Victor Law - Ricksoft Community Champion

Hi @Frances Shaw Welcome to the community. It will be depending if you want to restrict the READ only to specific users (login still required) or publicly accessible (anonymous access). If you are looking to set up READ ONLY access to specific users, then you can grant the users with Guest access as documented below:…

Hi @E , I think you may try to automate the Component creation via Automation with REST API web request or Groovy: * https://docs.atlassian.com/software/jira/docs/api/REST/9.12.12/#api/2/component-createComponent *…

Hi @Amelia Parnell Welcome to the community! Are you the project administrator of the Jira Project? By default, it is restricted to the Project Administrator and Jira Administrator. You may refer to the following document for more details:…

Hi @Dr_Win_ST Permission in each Jira project is defined according to the Permission Scheme associated with the project. You can define a project permission scheme associated with project roles in projects for easy management in the future. I strongly recommend you review the following document to understand the…

Hi @Claire Mayer Welcome to the community. Based on the error provided, it is clear that the customer who commented on the BSM project does NOT have permission to browse or view the linked TES Jira project. In this case, you may resolve the issue by updating the actor user to someone with permission to browse and edit the…

Hi @[deleted] It seems like you clicked on the workflow status. Please click on the arrow between the status for the workflow transition. https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/#Validators Thank you.

Hi @[deleted] Welcome to the community! Based on your use case scenario, setting the required field in the workflow validator is recommended instead of automating it. You may refer to the document below on configuring a required field on a workflow transition.…

Hi @guenter dlapa Welcome to the community. We are not the administrator and do not manage the Jira application. You should contact the Jira administrator to reactivate your account in the environment. Thank you.

Hi @federico I suggest you check with the organization admin if they have enabled the IP Allowlist for the Atlassian Cloud products. https://support.atlassian.com/security-and-access-policies/docs/specify-ip-addresses-for-product-access/ Thank you.

Hi @Revathi R K Atlassian Guard does not necessarily have the same number of licensed users as your Confluence environment, as your Confluence environment could contain users from other organizations or general email domain (e.g. gmail.com) user accounts. Hence, I strongly suggest you check the list of managed users in…

Hi @Greg McDonald I would strongly suggest you check with your Jira administrator and run an integrity check on the LexoRank as documented below to verify if there is any issue on the rank:…

Hi @Jonathan Welcome to the community! Based on the supported platform for Confluence v8.5, MSSQL 2022 is NOT supported and only supported from Confluence v8.7 and above. * Confluence v8.5.x supported platform * Confluence v8.7.x supported platform Thank you.

Hi @bhimashankar_poddar Have you tried importing the certificate into Java's truststore that Jira utilizes? Kindly refer to the steps below for importing the cert into the truststore: https://confluence.atlassian.com/kb/how-to-import-a-public-ssl-certificate-into-a-jvm-867025849.html Thank you.

Hi @Ron Moses Welcome to the community. It is possible to sort/change the order of the Request Types under the Portal settings page: Project settings > Portal settings > Portal groups Thank you.

Hi @IT Group Have you tried to bulk edit the Jira issues associated with the inactive users? https://confluence.atlassian.com/jirasoftwareserver/editing-multiple-issues-at-the-same-time-939938937.html Please note that you need the global Bulk Change permission to bulk edit/transition the issue to Close. Thank you.

Hi @Jason Pearce Welcome to the community! Based on the screenshot provided, the automation has been configured correctly. Please verify if you have added the Linked Issues field on the Creation screen for the target Jira project. I suspect the Linked Issues field has NOT been added to the Creation screen yet, and you…

Hi @AceCam Golf Welcome to the community. Have you tried checking on the https://admin.atlassian.com/ and verify if you successfully created the site with your account? There is a chance that you have claimed the site, and the site creation is still in progress. If the site creation takes more than 30 minutes to 1 hour, I…

Hi @Isabel L Welcome to the community! Parent and child Jira issue is more like a hierarchy structure and relationship between the Jira issues. Here is a basic example of the hierarchy structure: Epic > Story > Sub-task Perhaps you may refer to the following document to understand more about the Jira hierarchy:…

Hi @Jeran Fisher Jira DC v9.7.0 introduced a new behaviour change. For more information, refer to the following ticket: https://jira.atlassian.com/browse/JRASERVER-33123 Perhaps you may consider setting a dummy option like "-" for the child option if the value is meant to be empty. Thank you.

Hi @Eric Young Welcome to the community! I would suggest you reach out to one of the Atlassian Solution Partners, as most of the partners provide license management services and annual subscription quotes: https://partnerdirectory.atlassian.com/ Thank you.

Hi @Suraj Jha, Perhaps you may consider creating a manual trigger clone issue automation as below: https://confluence.atlassian.com/jirakb/automation-how-to-clone-tasks-stories-along-with-their-sub-tasks-1235853548.html Alternatively, you can manually clone an existing Jira issue or use the Issue Template app if you are…

Hi @Pineify Welcome to the community, According to Atlassian documentation, it is NOT listed as one of the supported languages in the code block macro. You may refer to the following document for your reference: https://support.atlassian.com/confluence-cloud/docs/insert-the-code-block-macro/ Thank you.

Hi @밍숫가루 I would suggest you contact Atlassian directly via the following portal: https://www.atlassian.com/company/contact/purchasing-licensing#/ The community does not have to control, manage, and refund the bill for Atlassian users. Thank you.

Hi @Warren Chan I suspect the Atlassian team is working on the feature, but it would be great to raise a ticket to check with the Atlassian team for confirmation. https://support.atlassian.com/contact/#/ On the other hand, I would like to add a column to indicate the criticality/ user impact so that any of us can mark down…

Hi @Warren Chan As far as I know, the Comment is not supported for Jira issues macro in Confluence Cloud: Kindly refer to the following Atlassian ticket for your reference: https://jira.atlassian.com/browse/CONFCLOUD-32764 Thank you.

Hi @Gira Desai The JQL provided in the previous post includes all the Jira issues created in the last 24 hours. Hence, it will still include some tickets from yesterday. If you are looking for a JQL query that focus on the tickets created Today (after 12:00 am), then you can try the following JQL instead: created >=…

Hi @Gira Desai Welcome to the Atlassian Community. Perhaps you can consider the following JQL query for issues created in the last 24 hours: created >= -24h Thank you.

Hi @Lara Arthur Perhaps you can consider configuring automation with the Scheduled trigger and a JQL query that runs daily and only includes any Jira issues approaching the date. Please refer to the following documentation for the Scheduled trigger for more information:…

Hi @Fatih Akkaya Only the Atlassian team can assist you with the reactivation. If you are unable to reactivate the subscription from the billing account, you will need to contact the Atlassian team to reactivate it. Thank you.

Hi @Deann Evans Jira standard projects are mainly managed via the project permission scheme, which associates a project role (recommended), group, or user with a specific permission. I strongly recommend that you check the project permission scheme associated with the project and identify which project role/group is…