Gor Greyan Expert

Hi @Siobhan.Claire.Lear Welcome to the Atlassian Community! You are not facing a bug - this behaviour is due to how your query logic works. To capture ticket that are both created and resolved in May 2025, you need the following JQL. resolved >= startOfMonth(-1) AND resolved <= endOfMonth(-1) AND created >=…

Hi @Mauricio Carvalho _ Suporte What did you get when trying my provided example? Could you please add "Log Action" before the action part and provide an example?

Hi @Andy Nabbs You can set just the Schedule Issue Trigger, which will be simply run with condition. Then you can set the conditions that I have provided.

@Nehal Majithia Thanks for the provided information. There can be different reasons why the update is not being done. 1. It can be run only for the owner, or when the owner is logged out, unverified, or the token has expired -> no refresh happens. 2. If the data is protected, it can be the reason for the refresh. Check if…

Hi @Nehal Majithia Welcome to the Atlassina Community! Can you provide more detailed information about the issue? Are you using a custom App Script or add-on to fetch Jira data?

@Ankit kharola Always glad to help.

Hi @Ankit kharola Yes, you need to download and re-upload the attachment content when cloning issues in a Forge app. In Jira, the attachments array contains metadata (Filename, MIME type, URL to download the file), but not the file content itself. So simply referencing the same attachment in a new issue won't work - Jira…

Dear @Jennifer Ness Above, I provide Screenshot, here, I will provide detailed information. 1. First, you should set the trigger, it is when the automation should start to work. I put there "Field Change" trigger, which is starting to work, when the Department field is changed. 2. You should set conditions. I used If/Else…

Hi @Jennifer Ness Welcome to the Atlassian Community! Yes, you can do it with Automation, using If/Else blocks and setting conditions, for each department and setting actions after each condition. If you want, I can provide an example with a screenshot.

Hi @Andy Nabbs You have raised an important question, which I have faced already :) When using the "Sprint Start" trigger, Jira requires a board to be selected, and the rule becomes limited for that project. You cannot currently apply a "Sprint Start" trigger to Project Category. You can use the following Workaround if it…

Hi @MrDo Please provide more detailed information. When did you receive these errors? What are you trying to do while getting this? 

Hi @Daniel Gavrila Thanks for the answer. There might be some reason why the automation will not work. 1. Check the all projects' Comment Permission. The actor should have permission to all projects. 2. In the Global Administration check, the rule is listed as "Global Rule". 3. Try to use the following body. Comment by:…

Hi @MRANJ Yes, it is not well for issue history :D Unfortunately, I don't know any other way for now, sorry for that :) 

Hi @Mary Ann becker If you are using Jira Misc Workflow Extension(JMWE) you can use the following Condition to reach your target. Use Related Issues Status Condition, like in the screenshot. If you don't have this add-on, please let me know, what add-ons you are using, maybe ScriptRunner?

Hi @Vamsi Fragale The Priority can be set or controlled in a few different ways, depending on whether you are using Team Managed or Company Managed projects. Here is a breakdown of where to check that. 1. Check the Project's Default Priority. Project Settings --> Priorities --> Default Priority 2. Check the automation;…

Hi @Mark Hansens You can read the Advanced Search documentation, which provides detailed information about JQLs and Advanced Search. https://support.atlassian.com/jira-software-cloud/docs/what-is-advanced-search-in-jira-cloud/

Hi @MRANJ Thanks for the reply. It should be worked via Listener. Go to Scriptrunner --> Listener --> Custom Listener Choose the Issue Linked Deleted event. (See the screenshot). Use the following script. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.link.IssueLink import…

Hey @Amy Schindel Thanks for the follow-up question. - If you use the add-on Dynamic Forms from Devinit, yes, once the "Data Load Needed" set to "Yes", the additional fields you have configured will appear on the same screen. - Yes, it is actually a very common add-on for Jira Service Management, where it works fine. Let…

Hey @Abi Williams Thanks for the information. Glad to hear that the issue is not actual anymore. You can accept the answer for further use. Thanks again.

Hi @philip_song This is the cleaned up version. Please try also this one. { "fields": { {{#if triggerIssue.customfield_15842}} "customfield_15842": { "id": "{{triggerIssue.customfield_15842.accountId}}" }{{#if triggerIssue.customfield_15851}},{{/if}} {{/if}} {{#if triggerIssue.customfield_15851}} "customfield_15851":…

Hi @MRANJ Thanks for the answer. Unfortunately, you can't restrict "link deletion" without affecting "create link" in native Jira. For an alternative solution, in Jira Data Center, you can use ScriptRunner. You can use Behaviours in Scriptrunner to hide/remove the "Delete link" UI element for specific groups or roles. If…

HI @Amy Schindel Unfortunately, Jira doesn't provide an opportunity to show a different screen based on field selection in transition. So, you can't open other screen from another screen. You can use the Dynamic Forms plugin from Deviniti, which provide the opportunity to open other fields based on one field selection in…

@Abi Williams Thanks for the answer. Will wait.

Dear @philip_song Thanks for your feedback. Could you please share log action, before the action, to see the result.

Hi @philip_song Try the following JSON. { "fields": { {{#if triggerIssue.customfield_15842}} "customfield_15842": { "id": "{{triggerIssue.customfield_15842.accountId}}" }{{#if triggerissue.customfield_15851}},{{/if}} {{/if}} {{#if triggerissue.customfield_15851}} "customfield_15851" : "{{triggerissue.customfield_15851}}"…

Hi @Amber Thomas Welcome to the Atlassian Community. The issues root cause may be different. I will tell some points to check, but also ask to provide an example from the mapping file, on how it is structured. 1. The Original Estimate field is part of the "Time Tracking" system. If your Epic's screen doesn't include the…

Hi @Yohann ROY Welcome to the Community. Unfortunately, in Jira, you cannot change the customfield type once it has been created. The limitation exists because different types of custom fields store data in different formats, and changing this type can lead to data loss or corruption. You can only change the name and…

Hi @Mark Bodha Try the following condition, maybe it will fit for your case. sprint not in (openSprints(), futureSprints()) AND sprint WAS IN openSprints() AND status = Ready to Work

Hi, @philip_song Thanks for the question. Try the following JSON. { {{#if(triggerIssue.customfield_15842)}} "customfield_15842": { "id": "{{triggerIssue.customfield_15842.accountId}}" } {{/}} } If the custom field isa user picker, then the accountId should work, if it is a single select list type, then try value instead of…