Kris Dewachter Community Champion

No, the data will not be migrated.

Hi @Sourav Mallick , In the CMA, you have to select which plugins you want to migrate. If there is no equivalent plugin in Cloud, the data will not be migrated. Best regards, Kris

Hi @Simon Matthews , There are some automation templates that can be used as an example. This one is a good one to start with: https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/1357359 The automation rule is executed 1x/dag, and looks for issues in status "Waiting for customer" that have not…

Hi @Johan Eltes , The easiest solution would probably be to set "Restrictions" on that specific page. https://support.atlassian.com/confluence-cloud/docs/add-or-remove-page-restrictions/ That way, you can define who is able to edit the page, and who is able to read-only. Best regards, Kris

@Kirsty Hood, the red-boxed one is the native. BR, Kris

Hi @Zainab , Are they not receiving any emails ? Or is it just some emails they are not receiving. Can you check the settings of the "Customer Notifications" ? Project settings --> Customer Notifications There is also a "Customer Notification log" in your JSM Project. The menu item is just below the "Project Settings" menu…

Hi @[deleted] , The Jira Service Management Standard plan supports up to 10.000 agents. So your next annual usertier would be 51-100 agents. Best regards, Kris

@Brian RatteCan you check the audit log of the automation rule to see if it actually executed and what has been done. You can also add the "Log Action" action to your automation rule to add some more logging.

@Brian Ratte, What is the trigger for the automation rule? Is it triggered each time a service is added ? Which service did you add last ? Was it "Dimension" ? Can you check if the automation rule was actually triggered and check what's in the logging.

Hi @Brian Ratte , In your "Edit issue" action, please make sure the label is "added" to the issue, and does not overwrite any existing label (ADDREMOVE). Best regards, Kris

Hi @gpadayogdog , Can you check if any of these smartvalues work for you : * {{issue.url}} - Returns the URL of the issue. * {{issue.url.customer}} - Returns the customer portal URL (for Jira Service Management requests) Best regards, Kris

Hi @AGT Online , Have a look at this documentation : https://support.atlassian.com/jira-service-management-cloud/docs/hide-email-signatures-in-the-issue-view-and-portals/ This allows you to hide signatures from imported emails. Best regards, Kris

Hi @David Ogier , as far as i'm aware, it's not possible to change the order of the addons. Best regards, Kris

Hi @Brian Ratte , You could try to create an "Advanced Branch" in your automation rule, that loops over the "Affected Services". For example, suppose you want to add a label with the name of each services to your ticket. You first create an "Advanced Branch" that retrieves the affected services from the issue with a smart…

Hi @Governança de TI , No, I don't think this is possible. The sequence of numbering can not be changed. The only way to have a different sequence would be to create a separate Jira project for the automatic tickets. May I ask what the purpose would be for the different numbering ? Best regards, Kris

Your best shot is to have a look at an external app. "Refined for Jira Cloud" might offer you what you need. https://marketplace.atlassian.com/apps/1218481/refined-for-jira-cloud?tab=overview&hosting=cloud

Hi @Lauren Ortiz , I would create an automation rule that sets the "Specialist" field upon creation of the issue. Best regards, Kris

Hi @Spartans , By default, there is no possibility to change the layout or the order of the fields in the portal view of a ticket. Best regards, Kris

Hi @Roland Uittenbogaard , The "Edit Request Type" action in the automation rule is trying to edit the trigger issue. You need to create a "Branch" in your automation rule to get the newly created issue first, and perform your 'Edit' action there. BR, Kris

@Roland Uittenbogaard , If you have a request type "Report a bug", then in your workflow, you should also fill the field "Request Type" with "Report a bug" and not "Bug"

Customers of the portal don't need a license. How are those issues created ? Who is the reporter of those issues ?

Hi @Roland Uittenbogaard , Is the request type correct? Do you have a request type named "Bug" ? Request types are not the same as issue types. What are your settings of the "Default Request Types" ? The documentation states this is used when changing the issue type of an existing issue. It doesn't mention anything about…

Hi @DJ Adamski , Do I understand correctly, that you want to make all issues in the project, visible to the anonymous customers in the portal? Since it's anonymous, and does not require a login, this is not possible. Best regards, Kris

Hi @Andrea Dieguez , I did a test on my environment and i experience the same issue. When you create a queue, and use the "Basic Search", it only lists the values of the global context. I think this is a bug in Jira. You can bypass this issue by switching to JQL search. When you use "Assigned Group" in the JQL, it will…

Hi @Andrea Dieguez , I'm presuming "Assigned Group" is a custom field ? Is this of a type "Select list" ? You can add different contexts for each project. Open the custom field --> Context and Default value --> Add new context In the context, you can define for which issue type and projects you want this context to apply.…

Hi @Risikanta Pradhan , I tried it myself and normally, it should work. Also, since it worked for the other attributes, I don't see why it doesn't work for the application attribute. Unfortunately, the error message does not provide much help. I would suggest to contact Atlassian support for this one. Best regards, Kris

Hi @Risikanta Pradhan , I don't see a way to remove the link with automation. What is the reason you can not remove the applications reference ? Do you get an error message ? Can you try removing the link attribute between the 2 object types, and recreate it again ? Best regards, Kris

Hi @Risikanta Pradhan , Do you want to remove the applications entirely, or just the inbound references ? Best regards, Kris

Hi @Dan Unfortunately, I must admit I don't have a clue anymore on why you are having this issue. The only thing I could suggest is to create an identical request type that you keep hidden, remove the old request type and migrate all the tickets to the new request type. But I can understand your reluctance to do that on a…

You don't have to set the trigger to "All users". You can set it to a specific usergroup. But offcourse you will have to be part of that usergroup in order to be able to trigger the automation rule. I presume that was your initial problem. You were not part of the usergroup set in the automation rule.