Manoj Kumar Gangwar Community Champion

Hi @Negin Heidari welcome to the community! At this time, Jira Cloud doesn't offer a direct toggle just for "Like" notifications. 

Hi @Osama welcome to the community! Jira Work Management projects are designed for business teams and do not natively support sprints (which are specific to Jira Software projects). If you're trying to work with sprints, you might be in the wrong project type. To work with sprints, ensure you are using a Jira Software…

Yes, they counted as a customer portal only. 

Hi @Maha Mohan In Jira Service Management (JSM), the display name customization for request forms is only applicable to the customer portal view. Unfortunately, Jira's issue view (the internal view used by agents) displays the standard field names rather than the custom display names configured in the request form. There…

Unfortunately, the default Confluence search, even with advanced search options like CQL, doesn't directly index content inside the database macro. The database macro is treated as a block of embedded content, meaning its data isn't parsed and indexed for search purposes in the same way that text is. You may check some…

Hi @Jason Chayer To automate the creation of a release in Jira Cloud when a build is created in GitHub, you can use GitHub Actions along with the Jira Cloud REST API. Here’s a detailed guide on how to set this up: Steps to Integrate GitHub with Jira Cloud 1. **Create an API Token in Jira Cloud**: - Go to your Jira account…

Hi @Alexander Demerson In Confluence, the data within a database created using the "Insert Database" macro isn't indexed in the same way that page content is. This means it may not be searchable using the standard search feature.

Hi @Vera Valshonok In JSM, customers added to the IP allowlist and those associated with Jira projects are generally considered "customers" only if they have access to the service portal. Portal Customers: These are users who interact with your service desk through the customer portal. They can raise requests, view the…

Hi @Kyle And Maya Vukmirovic welcome to the community! When you export a csv then all internal comments are marked ;Internal Access; so there must be a way to tell JSM anything with that is Internal Only and everything else is Comment for Customers. 

Hi @Jeremy Benson Welcome to the community! You can run a JQL query to check if the field has data from other projects then do not delete the context else you can delete it. you can run below JQL- Project != "your project name" AND "Field Name" is not empty

Hi @Viviane Moura Currently, it is not possible to export this report. We have a feature request suggesting the implementation of this option: * Export Satisfaction Report

What are the Release Approvers? Is it a user picker field or workflow status? What is the date field name to check the date is met? Based on that we can create the JQL or automation rule.

Hi @Shankar Please refer to the Atlassian University for free courses. https://university.atlassian.com/student/catalog/list?category_ids=21734-free-training

Hi @Sateesh Dara You can create a filter for issues that need approval and set up email subscriptions. Steps: * Create a Filter: Build a JQL query that identifies issues pending approval (e.g., status = "Pending Approval" AND releaseDate <= now()). * Save the Filter: Give it a name and save it. * Subscribe to the Filter:…

nope

Many test management plugins are available in the marketplace—for example, X-ray, Zypher, etc. which one you are using in your project to create the test cases then based on the plugin they have their own documentation to bulk import the test cases.

You can use {{issue.components.name}} and then select new components as well.

@Tejas Patil you can see the option at the right side to copy it.

Hi @AT Please follow the below doc. https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

Hi @Tejas Patil Could you please share the screenshot of your automation rule? We can Copy components from the Current Issue, Trigger Issue, Parent Issue, Epic, and Destination Issue.

Hi @Mar You might need to create separate custom fields for each Request Type. Edited: If you have the Scriptrunner plugin then you can use the behavior script in the workflow validator.

Hi @AT Welcome to the community! This is a Team-managed project and issue-level security is unavailable for those project types. You should still see the Issue Security option for Jira Work Management and Company-managed projects, but you cannot change them with the Free account.

Hi @Garigipati Murthy Welcome to the community! Could you please let us know which test management plugin you are using? 

Hi @Devin Liyanapathirana Welcome to the community!! First, please remove the field then go to the Issue view option and remove the field from there and save the changes. Then re-add the field again in the issue view save it. Now try to add the field under request type and check. 

Hi @AJohnston Please check the below doc. It may help https://community.atlassian.com/t5/Jira-Service-Management-articles/JSM-Approvals-by-Email-with-a-work-around/ba-p/1696674

Hi @Curtis Michael welcome to the community! You can use {{issue.key}} or {{issue.url}}

Hi @Callum Brown I have checked and it is opening in the same tab for me as well. Previously, If it was working fine for you then you can raise a ticket with them. https://support.atlassian.com/

Hi @Stephanie Humphrey The audit logs say that you have duplicate fields (Facility & Start date). Check the custom fields and search for both if found duplicated fields then remove the newly created ones or rename them to some other names. Maybe some other admin created it. The Assignee field is not added on the Issue…

@Pavankumar If this resolves your issue then accept the answer.

Hi @Pavankumar Yes, you can restrict Tempo time logging to specific issue types in Jira: You can add the properties on each status for a particular issue type. Go to Jira administration, then Issues > Workflows. Select the status to restrict, then click Properties. Add jira.permission.work.denied to the Property Key and…