Tansu Akdeniz Community Champion

You are right. Send e-mail action should be within the branch. Attaching the new one.

Hi @Jurica Petricevic Sample automation may guide you. Trigger the rule when subtask is transitioned. Then check other subtask statuses via JQL. If it matches, send an e-mail. Hope it helps.

You are welcome, glad you found the trigger.

Hi @Ariel Justiniano Welcome to community !! What about doing it in a one field? You can create a 'cascading select list' custom field without an add-on. Best

1- Which event is fired for status change? Generic event? The source of the mail could be a different place such as custom post-function, automation of service management or an installed add-on. You should check all custom configuration. Can you please check the e-mail body? Is it same as system mail templates? It may give…

Hi @Kenny Pun You need to give a license for each site (.atlassian.net). Because these are different Jira applications. It is possible to handle IT Helpdesk and HR service projects in same Jira. Then one license will be enough. Best

Hi @Şeyma Yıldız Welcome to community !!!

Welcome to community @cesar.alves 

Hi @Rob Horan Please check this link: https://support.atlassian.com/opsgenie/docs/integrate-opsgenie-with-jira/ Best

Hi @Sal If both teams are working in same project, go to the workflow scheme and assign your new workflow covering both issue types. In publish step, system will ask you to map statuses. Ex; If you delete an existing status which doesn't exist in new one, you need to map to new statuses. ps: There is no automated way to…

It makes sense. If SLA goal is given to only Task issue type then it won't start for service request. Please check this or attach a screenshot if possible. JQL have to cover all types which should count. Sample;

You said projects are identical but I want to be sure. Please check; * The existence of same issue type and priority in MNG project. * All those fields availability in MNG project create screen. * Validations and required fields in MNG project for creation. If everything seems fine, can you please only send summary and…

Hi @Veronika Uherková There are two notification in service desk projects. The one you shared belongs to agent notifications. There is also customer notifications which can be accessed from Project settings > Customer notifications. Which e-mail does she/he get? Please check this link.

Hi @Marco Gall I guess it is not possible by default. You can evaluate an add-on. Script Runner has some functions please check this link.

Hi @Eric Van Pyrz Can you please verify the existence of the fields for the creation in target Project B? There might be a config change. Please attach a screenshot from the automation if possible. Best

Hi @hiren.patel Welcome to community. It should work for auto-created too. Can you please share the SLA trigger and the issue? 

Welcome to the team !!!

Hi @Jackson Stubblefield Is it applicable for all browser? Is it possible to disable user installed add-ons and try it again? You can also create a ticket to Atlassian Support if problem continues. Best

You are welcome !!

Hi @jollroy Welcome to community. What is the error? It seems fine indeed. Try to test in script console for specific issue whose cf is not null. It should return select list value as string. import com.atlassian.jira.component.ComponentAccessor def customFieldManager = ComponentAccessor.getCustomFieldManager(); def issue…

Hi @Yasser AbdelMoniem Welcome to community. Alternatively, you can use one single project to handle all client tickets. So, customers will create a ticket in unified project and all tickets will be handled in queues section by agents. You can create an "Organization" for each client and group users. Then define different…

Hi @Yasser AbdelMoniem Welcome to community. There is public doc which may help you. Please check this link. Best

Hi @IT Department Please try this. {{issue.comments.last}} Best regards 

Hi @Stefan Bosman Please check this link to add a comment. There is an example for curl. For Jira cloud, url should be like "https://your-domain.atlassian.com/rest/api/3/issue/{issueIdOrKey}/comment"

Hi @Wendy du Preez You should see this "Move" button on issue view screen. In order to move an issue, you need to have a "Move Issues" permission. Please check this from project -> settings -> permissions. Best

Hi @Jovin Risch Welcome to community. Please check this link. Since it is cloud version, you should be able to change your avatar over MAC account. Best

Hi @sgole I think it is not possible with Behaviours code. It only works in pop-up's such as Create and Edit issue screens. If a custom field is added to issue view screen and has a value, it is always shown. You can not hide it depending on other field.

Hi, You can simply use * Approvers = currentUser() OR * Approvers = userA What do you want to search specifically?

Hi @Alex Larini 1) TO VIEW: Yes, you can restrict the people to see limited issues in same project. One solution is to create an issue security scheme for your project. Let's say: "General" (default) and "Project Managers" security levels. Any issue created from portal gets "General" security level and it is shown to all…

It is from server/DC.