Gaurav_0av1h6 Expert

Hello @Adam Foot From the error message shared, it seems that some information is being missed by the rule or the rule does not have permission to execute the transition. Kindly check the permissions.

Hello @Mariano I do not think that there is any way to specify all company members in a single rule unless all your company members have a unique identified and set up maybe like <company_name - employee_name>. Also, I have not yet come across any cheat sheet and refer to the documentation every time. It is a good idea for…

Hello @Mariano I understand your use case which is a classic example of customer support. I would suggest having a transition from OPEN to the desired (WAITING FOR CUSTOMER) status. Just a caution here, the conditions used (External Comment and Status as OPEN), would trigger the issue to change status to WAITING FOR…

Hello @Jack Howard There is an indentation in the automation created by me as I am using the 'If-Else' statements while you are directly checking the Issue Type. Logically, both will work in the same manner but as you are not using the 'If-Else' construct, it will check for each condition which might take a little bit…

Hello @Jack Howard Welcome to the Atlassian community!! This is achievable using automation. From the Project Settings navigate to Automation and create a new rule. Please refer to the below screenshot for the detailed set-up of the rule. This can be extended or customized as per your requirements. Please accept the answer…

Hello @Adam Foot I have just tried using automation to achieve something similar, but not perfect. The automation would check for attachment any time an issue is transitioned from Status A to Staus B. This would take into consideration any attachment added to the issue, previously as well. If the attachment is missing it…

Hello @Adam Foot To add a screen to the Transition, please open the workflow in edit mode, select the required Transition and click edit. From the dialogue box select the required screen and click Save. Please accept the answer if this helps solve your query else respond and allow others to share input.

Hello @Ganesh This can be accomplished by creating automation where you can define the default values which would be set any time an issue is created in the specified project. Please accept the answer if this helps solve your query else respond and allow others to share input.

Hello @Adam Foot An alternate option would be to add a screen to the transition which makes adding an attachment mandatory. This will also need admin privileges. Please accept the answer if this helps solve your query else respond and allow others to share input.

Hello @Colleen Welcome to the Atlassian community!! To overcome this problem, these fields (Host Name, Issue Source, and Terminal Model) will need to be set to a value by the Automation. Probably you can define some default value and set that, which later can be changed to the exact value. Please accept the answer if this…

@Keenan McCraryyou would need an actual team member or colleague who could be a watcher, similar to a real-life scenario.

Hello @Keenan McCrary The issue creator is usually not notified of their own changes. You can check this from the Notification Helper. I would suggest you test this with a team member. Please accept the answer if this helps solve your query else respond and allow others to share input.

Hello @Jairaj K For separate reasons, you will need to set the Resolutions these statuses. This will require admin privileges. The steps are: * From Project Settings, go to Workflows * Choose the workflow, which is applicable and click the small pencil-like icon on the right-hand side * Click on the diagram, to view the…

Hello @Keenan McCrary This is great, you are ahead of me. As you are using a custom field to capture the Watchers, you can edit the Notification Scheme to send Issue Create notification to the Watchers. Please find below the screenshot for the same. Let me know if this helps. Please accept the answer if this helps solve…

Hello @Keenan McCrary Currently, the default Watchers cannot be added to the Issue Create. The alternate option for this is documented by Atlassian here. Please accept the answer if this helps solve your query else respond and allow others to share input.

Hello @Hanieh Katebian The creation of Tasks for an Epic can also be automated. Please refer to the attached screenshot. This is a sample implementation that creates a Task whenever an Epic is created with appropriate links as well. This also triggered the other automation for Sub-Task creation. If required these two can…

Hello @Hanieh Katebian The native Jira functionality does not allow the child tasks to be cloned with the Epic. Are you using an add-on to clone the child tasks with the Epic? It could be one of the reasons that automation is not behaving the way it should. If you are creating the Epic in the same Jira project, then I…

Hello @Hanieh Katebian As the automation for sub-task is triggered when a Task is created, it considers the Task as the issue. Hence, when we say, {{issue.parent.epic.summary}}, the automation is unable to understand as the Task has Epic as the parent. Update the automation with '{{issue.epic.summary}} : {{issue.summary}}…

@Jorge Vea, Could you please share the screenshot for the SLA setup? This will help in understanding the issue.

Hello @Roy Mishal In case a new SLACK channel has been created, you can accommodate it by editing the existing rule or by creating a new rule. Alternatively, you can even create a custom field in Jira where the user mentions the channel name and then you can use that directly in the automation. This way, you will not need…

Hello @Roy Mishal I do not have an example readily available to share with you at this point. I have implemented it previously, and when we mention the specific channel in the automation, it will be posted to the exact channel. Kindly refer to the Atlassian documentation related to this, here. Please accept the answer if…

Hello @Roy Mishal Welcome to the Atlassian community!! This use-case is possible using an if-else construct in a single automation rule. Please find attached the screenshot which depicts this. The components are being used to differentiate the channels. This can be customized as per your requirements. Kindly let me know if…

Hello @Adam Foot To ensure that the transition happens from status A to status B only if it has an attachment, please add a validator to the transition. Please refer to the below screenshot for implementation. NOTE: This will require admin privileges. Kindly contact the instance administrator for this. Please accept the…

Hello @Vera Kim The issue being checked 'AZO-651' is an Epic that will not have any sub-tasks associated with it. The rule would be applicable to other issue types, like Story or Task. In case you need the Epic to be auto closed, then the automation would need to be updated or a separate one would need to be created.…

Hello @sandhya sandy Welcome to the Atlassian community!! To create an attachment, excel or any other, click on the 'Insert files or images' or press 'Ctrl+M' which will open the dialogue box from where can navigate to the file location and upload as an attachment to the confluence page. Please refer to the screenshots.…

Hello @CHEN How Welcome to the community!! This is a really interesting question and something which I can replicate. The challenge is as soon as we try to use the saved filter as 'filter = "calculator_aggregated_effort" '. In the documentation from Adaptavist, it is mentioned that the calculation is not saved anywhere. In…

Hello @sriharsha m In Jira Service Management, the APIs can help us to post the comments specific to customers or keep those internal. The tag of this is 'public' which is boolean and can be set as either 'true' or 'false' which will comment is shared with the customer or otherwise. The API documentation from Atlassian is…

Hello @Keenan McCrary As the watchers are being added after the creation of the issue, the issue creation notification would not be sent to them. An alternate would be to set the watchers while creating the issue itself and include the watchers in the notification for issue creation.

Hello @Service Account As the number of approvers is not pre-defined, we will not be able to build it into the workflow. In case you have can define the process with specific approval levels, then the workflow can be customised to cater to them and will help you to retrieve the approval timestamp.

Hello @Harshada Pawar Currently, the date time of approval is not captured in Jira Service Management. As an alternate, you can have different status for approvals which will help you capture the date time for example, if you need approval from 3 Managers, you can have 3 different status and transition them on approval.…