Florian Bonniec Community Champion

based on teh screenshot you provided you send {{Region}} not {{Region.urlEncode}}

Based on the screenshot you apply .urlencode to OS only not Region nor VM SKU

The web request action seems to worked well, the issue is when you try to add probably the response as comment to the issue no ?

Do you have a screenshot of the automation action ?

Hi @Sairam Adla What is the smart value you are using ? What is the expected vs actual result ? Regards

Hi @PARISATO Marie-Hélène I think the one you mention is the one that is pretty close to what you currently have. I'm currently using the same app as you are and will have to switch at some point as DOIT BI is no longer available. They seems to be a copy, one from the other. Regards

Hi @ryang_sei As this question is related to JIRA Forge, I suggest you to ask your question on the developer community. The Atlassian Developer Community Regards

Hi @Andreas Kemper From https://admin.atlassian.com/ you should be able to go to Billing, on Atlassian Guard line, you should have Manage. Then on the top right, you will have Cancel Subscription in the ... menu next to Change plan. Regards

HI @nalams Why do you need to hide them ? Could you remove them by creating a dedicated Issue Type Scheme for this project instead ? Regards

What is the query use in the board ? Does it include the subtask issue type ?

Hi @Saumya Mishra If it's a Scrum board it's normal that it's not displayed in the backlog, but should be displayed in the current sprint section. It's because it do not make sense to plan a story without all the subtasks under it. Regards

Hi @Abhay Kulkarni It's a global configuration so you need to be JIRA Administrator in order to do that. The kb below should help you to achieve whay you are looking for. https://support.atlassian.com/jira-software-cloud/docs/configure-custom-hierarchy-levels-in-advanced-roadmaps/ Regards

This config looks good to me. When someone create a request from email with CC, are the CC added as participant in the created ticket ? You should see them under the reporter in the ticket on the portal view of the ticket.

HI @Ashley Honeycutt You could use Automation and Scriptrunner for this. Create an automation based on edit event of the fields that are use for Approval status. Then when it happen, you use the Scriptrunner action. The script could looks like: import com.atlassian.jira.component.ComponentAccessor import…

Hi @Abdallah Ahmed Are the CC added as participants in the created request ? https://support.atlassian.com/jira-service-management-cloud/docs/add-request-participants-through-email/ In the project settings, Notifications, Customer Notification, when you edit one of the template, what is configured in the To section ?…

Hi @Samuel Srungarapati How do you create the new issue ? Listener, post function or something else ? What is the script use for creating the new issue ? Regards

Hi @Mayur Gaikwad/Tech PMO You can find the documentation below: Configure workflow schemes | Atlassian Support About data collected, the data will remain in the fields it has been stored in, so it will not be wiped Regards

Hi @Grunspan Macarena The limit is 32767 characters https://jira.atlassian.com/browse/JRACLOUD-63007 Regards

Hi @Shannon Hoskins If you have configured the exact same screen in the workflow, and they show up to the user differently, it's most likely because there is a context on the custom field that did not show up. You just need to add the new project in the customfield context. Regards

Hi @Samuel Holley I suggest you to use HAPI from Scriptrunner instead. Create Issues <span> // cascading select</span><span>12 setCustomFieldValue('CascadingSelect', 'BBB', 'B2')</span> Update the Value of Custom Fields through the Script Console Regards

Not sure, the issue could most likely because there is multiple Sprint in the Sprint field and it may take the wrong one. {{issue.Sprint.last.startDate.jiradate}} maybe

Hi @Eric Dyer Have you try to add Re-fetch Issue data action before ? Regards

Hi @Antoine _Klee Group_ You need to import import com.atlassian.jira.jql.parser.JqlQueryParser Regards

Hi @Ia g This is a community forum. You can ask your organization admin to switch plan. https://admin.atlassian.com/ Billing > Select you product and click on Manage then switch plan. Regards

If you updated the workflow, you just need to published it. If it's a new workflow you created, you need to associate it in the workflow scheme. https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-workflows/ Regards

Hi @Julian Haines Are you using '10 Apr 2025' or 2024-04-10 ? From the screenshot it seems to be '10 Apr 2025' Regards

You may have to reach out to your JIRA product admin to configure the workflow properly. 

Hi @Isabel Cruz This is not possible as far as I know. Regards

From the project settings, you need to go in Workflow section on the left navigation bar. Then Edit Workflow, select the one associated with the issue type you need to update the workflow for. Then add a post-function Select Update Issue Field Regards

It's configuration, so you need to be project admin or jira admin depending on the type of project or if workflows are shared or not. https://support.atlassian.com/jira-cloud-administration/docs/edit-an-issue-workflow/