Bill Sheboy Expert

Hi @Daniel Loewenstein It may help if you post the complete rule that you believe to be failing, with your included log statements and audit log output. That might reveal if this is a rule processing/logic issue rather than the condition not working as expected. Thanks!

You may confirm what Jack said by writing this to the log: {{initiator.displayName}} Which is the name of the triggering user.

Please try to just type TRUE, and tab off the field. That worked for me.

Sorry, I just noted in the rule you were trying to transition the issue *and* assign to the triggering user. I left off the transition part.

Hi... My understanding is that Branch Created fires when an issue key is included in the name... So it appears the Assignee has not context yet. How about this: * Trigger: Branch created * Extract the key from the {{branch.name}} storing the value in a Create Variable * Branch on JQL for that key in the created variable*…

Hmmm... I just recreated that rule, and I found it. Try this. Delete the edit, save your rule, publish, disable it (just in case...) and then try to re-add the Edit Issue.

Hi @[deleted] There is an open suggestion to add the user-based information to the development triggers, which you may view here: https://codebarrel.atlassian.net/browse/AUT-1997 Best regards, Bill

Hopefully this one will get fixed sooner... Those search/filter defects are bad because they lead us down different paths looking for fixes. __Bill

You almost have it done... you want to set Flagged to TRUE in the Edit Issue.

Hi @jonatan.siden Regarding detection of a custom field change, you probably aren't going to be able to do that with out-of-the-box JQL. Have you looked in the Field Value Changed trigger in automation rules to see if your field is listed? That would be the easiest way to detect this, and then take action...perhaps all the…

Thanks for clarifying. Okay, I will assume when you create a bug, that you link it to a story before saving. If so, this will do it: * Trigger: Issue Created * Condition: Issue Type equals Bug * Branch: For linked issues to the triggering issue * Condition: Issue Type equals Story * Edit issue: set Flagged to TRUE If you…

Hi @Deepak Parambath -- Welcome to the Atlassian Community! Would you also please include an image of your audit log entry showing the errors? That will help the community provide ideas. Thank you. Best regards, Bill

Parent only works with NextGen, but Epic Link works with Classic. However it appears that you have custom issue types; that is why I was asking about your hierarchy. If neither Parent nor Epic Link will work for your issue types, you can still use Branch with JQL to match the items, and then make the transition update.…

Hi @Claire Dufetrelle -- Welcome to the Atlassian Community! There is nothing built into the cloud version of Jira to do this. Here are several suggestions to add this feature, which you may review and vote for:…

Hi @jonatan.siden -- Welcome to the Atlassian Community! As you note, the CHANGED operator only works for a limited number of fields, and not custom fields. I do not believe you can do this with out-of-the-box JQL. Have you considered investigating the marketplace for scripting add-ons? Without getting into what your…

Thanks for that information. As follow-up questions: Is this a Classic or NexGen project? (Parent field only works for NextGen, I believe.) Please describe the issueType hierarchy you are trying to use, as it appears you have some custom types here.

Hi @Luiz Alves Filho If you are manually linking when you create the Bug, you can then use automation to set the flag (edit issue, setting the Flagged field to True). If you are looking for a way to automatically link the Bug to the Story, using automation, you would need some way to uniquely identify the Story for the…

Hi @Ahmad Sidawi Your rule in the image does not seem to match what you are asking. Have you tried something like this: * Trigger: issue transition to Scheduled * Branch: parent of issue* Then Transition the issue to: copy from trigger issue Best regards, Bill

Hi, If you change your browser settings you can change the default location or change it to prompt you for a location for each save. __Bill

Hi @Bethany Holt I did a quick search and did not find anything on the community forum or in the public backlog for this symptom, and I suggest that you create a support ticket for it: https://support.atlassian.com/contact/#/ Best regards, Bill

Hi @Paul Wieland According to these two suggestions, that is not yet possible with the REST API: https://jira.atlassian.com/browse/JRACLOUD-59948 https://jira.atlassian.com/browse/JRACLOUD-45929 Best regards, Bill

Hi @Luiz Alves Filho Maybe... How do you know a defect (bug) is related to another issue within Jira? If it is a sub-task type or is linked to the "parent" issue then you should be able to use an automation rule to detect the condition and then flag it. You would also configure your workflow to check for the blocking item…

I do not know if the iterator issue is legacy versus new automation related... The "new" automation in JSD (Automation for Jira) does support iterators, as there is an example in one of the documentation pages showing the use of {{#issues... }} processing after a scheduled JQL trigger. Regarding the supported smart value…

Hi @Clare Butcher How you capture your Behavior Driven Development (BDD) scenarios may depend upon how your team is defining the scenarios. If they are all stand-alone, customer facing, you could split each into a task/story. If not, please consider one of the testing addon tools to better manage the scenarios and the…

Hi @Mike Wilding -- Welcome to the Atlassian Community! I just tried this for a Classic project with Chrome browser and it worked for me. What are you seeing when you use the right-click menu? Best regards, Bill

Thanks, @Darryl Lee I previously submitted a related defect, that smart values (issue or variable) do not work within an iterator. For example: {{#issues}}* {{key}}, elapsed days: {{created.diff(now).days}} {{/}} I heard back, "not intended to work that way; functions as designed." More generally, the supported automation…

Hi @Manuel Martín-Vivaldi Do you have any NextGen projects with these sub-tasks? If so, there is an open defect preventing the search of the sub-tasks when also filtering by Sprint. You may view and vote for this defect's resolution here: https://jira.atlassian.com/browse/JSWCLOUD-18394 Best regards, Bill

Here is the suggestion to add email notification on a reaction: https://jira.atlassian.com/browse/JRACLOUD-73648

Hi @Suma Kustagi What version of Excel are you using? After Microsoft made a change a while ago to protect against downloaded internet files, CSV files could open as blank/empty in Excel 2016 and earlier. The suggested fix is to: * Select a download location other than the default MyDownloads folder, ensuring that you…

Hi @Mark Collins Also, here are some of the suggestions to add filter options for initiatives, which you may review and vote for:…