Bill Sheboy Expert

Hi @Jon Reafsnyder Please try using the Epic's Key value for searches with parentEpic, such as parentEpic = myKey-123 Please look here for more information about parentEpic: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/ Best regards, Bill

Hi @lisa To add to @G subramanyam suggestion, you may need multiple rules for this because the parent/child relationships are different for different issue types. For example, the rule below works for starting an Epic into in-progress for any child Story or Bug issues: You would need a separate rule for story/sub-tasks and…

Hi @Vitalij Kacanovskij -- Welcome to the Atlassian Community! In addition to Jack's idea, there is an open suggestion to add the sprint goal to the board, which you may watch/vote for here: https://jira.atlassian.com/browse/JRACLOUD-40699 Best regards, Bill

Hi @Sebastian Jopen Until that suggestion is implemented... As a work-around you could add a couple of manually triggered automation rules, one to set and one to clear Flagged. You may run the rule directly from the issue view. Please look here to learn more about automation rules:…

Hi @Chris Puffe I do not believe that you can perform that type of query with out-of-the-box JQL. It would require checking the status of children to select their parents. There are marketplace add-ons for JQL scripting which could help do this, such as ScriptRunner. And... Your existing query uses AND and OR statements,…

Sure, I will try to help with more details. I see that you are using a JQL statement to limit your scheduled trigger in the rule. After the trigger, you may add the LookupIssues action, and use the same JQL. Then your email body may use the LookupIssues results. So your rule pieces, in order, would be: * Trigger: Scheduled…

Hi @PIERGIORGIO.RETTAROLI -- Welcome to the Atlassian Community! Please try this JQL to find those tasks, substituting in your project name, status, and date range: project = myProjectName AND status WAS "my status" DURING ("2021-01-01", "2021-01-20") ORDER BY Key The query should return the list and you may see the count…

Hi... Did you notice that the radio buttons immediately above, for other options, also appear to be missing on that view?

Yes, and... if you just need to list by component to work with the set, use a dashboard and a gadget on your board's filter and Component. You can select/view them as needed. Best regards, Bill

Hi @Rich Coleman Are you just trying to copy the links from the triggering issue? If so, please change your clone action for the Linked Issues field to use Copy Linked Issues from Current Issue. You may find that with the ... at the right side of the field in the Clone action. Best regards, Bill

Hi @ankit45621 Sorry, I do not know that. I suggest waiting to see if the person from Atlassian who responded has more information. If you do not hear anything back for a while, consider submitting a support ticket for help. Best regards, Bill

For your use case where you appear to want sequential processing after the issue creates, you can try what @wwalser suggests by eliminating the branches. If that will not work, the alternative is to use multiple rules, where the creation of the issues sets an indicator in them which you can detect to trigger a second rule…

Thanks for that information. The approach I was suggesting would automatically record the date/time an issue was flagged. Once set, you can filter on the custom field as you asked. Instead it appears you want to manually set a Flagged Date, which may be different from when the issue is flagged in Jira. I do not belive you…

Hi, Holly. That is where LookupIssue can help. You use it with your JQL, and it treats the results as a set. For example, this would list the keys for them all, which could be sent in one message: {{#lookupIssues}}* {{key}}{{/}} Please look here to see which fields are available for LookupIssues:…

Hi @Javier Yuste Are you asking if there is a way to see when an issue was marked as Flagged? In a separate "window"/pane? If so, the separate window/pane isn't possible, I believe. Seeing when an issue was Flagged is possible by adding a custom field, perhaps FlaggedDate, and use an automation rule to set the field. Then,…

Hi @Holly Schomann You can do this with Automation for Jira, creating a scheduled trigger rule, use Lookup Issues with your JQL search, and send the message to Slack. Please look here for information to get you started:…

Hi there, Our site admin just independently raised this as a defect to Atlassian yesterday, as it is breaking some marketplace vendors' dashboard gadgets that rely upon status and status category searches. The root cause appears to be a change where status ID numbers can be searched uniquely but status names are not…

Hi @Fowler There are several open suggestions I found to add that capability to distiguish backlog and board for Next-Gen projects. You may watch/vote for them. * https://jira.atlassian.com/browse/JSWCLOUD-17786 * https://jira.atlassian.com/browse/JSWCLOUD-17892 * https://jira.atlassian.com/browse/JSWCLOUD-18760 *…

Hi @Ernesto Rodriguez I expect you may see some responses about "best practices". Instead, l have some practical delivery-based thoughts I hope can help. (And, I don't believe in best practices; only better ones. :^) Short answer is you may be able to do this, and it may not help with the problem you describe wanting to…

Thanks for that information. You should be able to update the filter using the guidance from @Trudy P Claspill to do that. You will need Project Admin permissions for that.

Hi @Julia Foden Have you tried nesting the tests? Perhaps something like this (assuming your field is called Risk and appears to be text): {{#if(issue.Risk.value.asNumber.gte(4))}}{{#if(issue.Risk.value.asNumber.lt(7))}}Medium Risk{{/}}{{/}} And maybe skip the && and just put all the tests end to end, knowing that at least…

Hi @Andie Duframe Would you please post your entire rule and an audit log for where you see the problem? That may provide some context. Thanks! Regarding the branch execution, I wonder if you have hit an edge case. Please consider this…

Hi @Daniel Newman Would you please post an image of your rule and audit log so we can see where you are having an issue? Just to confirm, Lookup Issues can work for JQL anywhere in the rule. Its strengths are the ability to create dynamic JQL based upon smart values, and to process the items as a single chunk, such as with…

Hi @Alan Au After you submit the defect, please post a link to it so others may follow it. I did not see this symptom listed under the parent new issue list item: https://jira.atlassian.com/browse/JRACLOUD-70555 Thanks, and best regards, Bill

Hi @wwalser Thank you very much for your well-explained response, and reality-based ideas of possible fault points. I truly appreciate the excellent work your team does for Atlassian and the users in the community. In addition to what you describe as catch-up/recovery processing following an automation impacting incident,…

Hi @raviteja567711 I suspect that yes, you may do all those things with an automation rule. The triggers and actions are different in the server and cloud versions. And, there is a "lite" version of automation and a full version for server. Please look at this documentation to get you started:…

Hi @Sergey Kopch -- Welcome to the Atlassian Community! What mind mapping tool are you using and what export capabilities does it have? Jira cloud can import issues, so if you can export from the mind map you could import the results to Jira. You may also want to check the Jira marketplace to see if there is an existing…

Hi @Steph -- Welcome to the Atlassian Community! There is no built-in way to remove this message yet. Here are two suggestions to add the disable option, which you may watch/vote for: https://jira.atlassian.com/browse/JSWCLOUD-21021 https://jira.atlassian.com/browse/API-274 Best regards, Bill

Hi @Divya Gupta -- Welcome to the Atlassian Community! Would you please answer the following the help the community provide you with suggestions? Are you using server or cloud version of Jira? Is your project type Classic or Next-Gen? It appears you want to remove the Story type issues from the board and keep just the…

Hi @[deleted] For a filter like that, Jira cannot easily determine which projects are included (even when we can just look and see that). Please look at this article which describes how to handle those cases: https://support.atlassian.com/jira-cloud-administration/docs/use-manage-sprints-permission-for-advanced-cases/ Best…