Kris Dewachter Community Champion

Hi @Alicia Ochovo , What is the content of the field ? Does it display different information based on the logged-in user ? Best regards, Kris

Hi @Mathew Lederman , If I understand correctly, in the first step, you remove the "list of approvers level 1". And in the second step, you re-add them ? Where is the value with the list of approvers coming from ? Do you copy it from the original issue? Which you just removed ? Maybe you should save the value in a variable…

Hi @Dharma Teja _Appfire_ , Where are you using this AQL ? There is no way to specify specific columns (like you can in sql). You can change your view to display the columns you need. Best regards, Kris

Hi @Kishor Mudhili , I'm not sure I fully understand your question. Doesn't this depend on the workflow you assign to your 'Change' issue type ? Just make sure there is no approval step in your workflow. Or create an automation rule that automatically approves a change if certain conditions are met. Best regards, Kris

Hi @James Gray , What format does your calculated date have now ? Can you display the value in the automation rule log ? I think it will look something like this. I think the best way to handle this is to put the calculated date in a variable first in the automation rule, and perform a date formatting on it. See this page…

@steven.allcock, Correct, It will look over every object from the 'Lookup Objects' action. You can have a look at this documentation : https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935 Br, Kris

Hi @steven.allcock , I think you need to add a "For Each: Branch" node after the "Lookup objects" node, and loop over each item separately. Best regards, Kris

Hi @Beyer Gertrud , Your only option would be to use Atlassian Access. Best regards, Kris

Hi @Paweł Grams , My guess is that the API integration is not setting the correct value for that field when creating the ticket. And therefor it falls back on a default value (being "portal"). Best regards, Kris

Hi @Renato Seiti Tsuchida , I think a simple automation rule would work in this case. * Trigger : Any changes to the 'Satisfaction' field * To check if the satisfaction rating is below 3, you need a if-statement with a JQL : satisfaction < 3 * Action : Send the email For your second question. It's not possible to add…

Hi @Stefaan Boes , I think this ticket might be related to your issue https://jira.atlassian.com/browse/JRACLOUD-75009 "Teams" and "Zoom" is mentioned in the issue comments. Best regards, Kris

Hi @Sandesh TM , Assuming you have a custom radio field called "Test Radio Button", with possible values "Yes" and "No". If you want to hide the transition when "No" is selected, add a "Value Field" condition to the transition and configure it like in the screenshot below. I hope this works. Best regards, Kris

Hi @Stefaan Boes , Can you check if you have 'Zoom' enabled in your project settings ? You need to be the project admin to enable or disable Zoom for a project. * From the navigation on the left, select Project settings > Incident management. * Under Communication preferences, switch on or off the Zoom option. If disabled,…

Hi @Ramazan Keskin , Please have a look at this automation rule template : https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/1357359 Best regards, Kris

Hi @Sandesh TM , Can you explain your question a bit more in detail ? Do you want to hide the issue status from the detail screen ? If so, I don't think this is possible. Or do you want to hide a certain workflow transition in the detail screen? This can indeed be done with a workflow validator on the transition (Field…

Hi @Nuno Lopes , Can you try this JQL ? assignee in membersOf("A") and component = CA Best regards, Kris

Hi @Sarah Ergen , Have a look at the configuration of your board. In the "Columns" section. Maybe the "Ready To Deploy" status is mapped to the "Backlog" column. Best regards, kris

Hi @Dipti Sinha , The possibilities of editing the layout of the portal are very limited. You can not remove these fields. Your only option to edit the portal layout is to look for an additional addon in the marketplace (ex. Refined for Jira Service Management Cloud) Best regards, Kris

Hi @ITDept , Do I understand correctly that you want to add the "Due Date" in this customer issue list in the portal ? You can do this as follows: * As an jira admin, navigate to the portal * Navigate to the requests list * Click the "Customize" button on the right of the screen * Select the fields you want to display.…

Hi @Shanara Sadeque , As far as I know, there is currently no possibility to include custom fields or even the comment field in the approval process. Best regards, Kris

Hi @Todd Hesson , There is no straightforward way to retrieve form information. I see 2 possible ways : First method is getting the information by API calls: This is information about the forms api - https://developer.atlassian.com/cloud/forms/rest/intro/#about And this is more information about using API calls in an…

Hi @Jehan Bhathena , Thanks for your reply and suggestions. Unfortunately, giving the user JSM Agent permissions, still does not allow me to add him to the team. And in the developer tools, no network errors appear. I'm going to log this one at Atlassian support. Maybe they can figure out what is going on. Will post the…

Hi @Tim Kappel , The timeline view is linked to a board. You can create your own saved filter and link this to the board. This will also change the timeline view. Best regards, Kris

I don't know.

Can you try navigating to your "Project Settings" --> "Automation" --> "Global Administration" (located left of the "Create Rule" button". When you create a rule here, you should be able to see the asset triggers.

Hi @Namrata S Dyaganatti , I assume the field configuration for SR's and Incidents are different. They are using different fields, and are therefore not displayed. Or the fields are not included on the sceens. Best regards, Kris

Hi @Noemi Pallotti , The settings in the notification scheme are only used to send messages to users with an Atlassian product license (Agents, Administrators, Developers, ...). Portal customers only receive the emails that are configured under "Customer notifications" Best regards, Kris

Hi @Paul Nguyen Yes, change management is part of the default functionality of JSM Best regards, Kris

Hi @Jeyhun Gayibov , It's not yet possible to copy SandBox settings to Production. It would be a cool feature however. You can vote for it here https://jira.atlassian.com/browse/CLOUD-11150 Best regards, Kris

Hi @Ayush Lawania , The fields in the form only exist in the form. You can not see them in the issue view, or use them for searching, reporting, etc .... If there is information in the form you need for reporting, you need to create a custom field for it in Jira. You can then use this custom field in the form. It's also…