Bill Sheboy Expert

Hi, Liam. Essentially you create a component for each team, create and save a filter which returns issues just for that team's component, and then create a board from the saved filter. An example filter would be: project = MyProjectName and component = MyTeamAComponent ORDER BY Rank ASC Here are some support references to…

Hi, Sari! The thing about quick filters (and Kanban board sub-filters) is they add onto the existing board filter; they do not replace it. So the issues may have already been excluded by the board filter. One possible work-around is to make your board filter less specific, and then use the quick filters to limit what is…

Hi, David! Wow, that's a lotta loops if you are hitting that limit. And, it could mean that some of your intended executions will not fire (and so be lost due to loop detection). I am curious: what is your use case/problem you are solving, which is causing this symptom? For example, is it a lot of data and batch…

Patricia, in the second rule you reference... https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/140671/25000987 Please note there is a related issues condition. That is what checks that all of the subtasks are done before moving the parent to done.

Hi @Jiri Komarek -- Welcome to the Atlassian Community! I was curious about this one and so retested it...Short version: it still doesn't work Longer version: * According to this how-to for finding the smart values for a field, the emailAddress of People fields for a team-managed project is available to the REST…

Hi @Jira user Would you please explain the problem you are trying to solve? I ask as teams using Kanban methods do not usually have the idea of a Sprint in their working methods. Kanban teams pull work based on capacity, and Scrum teams limit work based upon what they planned for the Sprint. How would showing a team's…

Hi @PATRICIA MURPHY Adding to what Jack suggests and your question, the two example rules you note will do exactly what you requested. What part is missing for you need? You would only need the if/else rule component when you want to combine these and perform the operation in one rule. Kind regards, Bill

Sorry, I don't use that field type often and forgot that. There is a suggestion to add built-in support for those field operations: https://jira.atlassian.com/browse/JRACLOUD-74280 Until that is available... The work-around if you are using Jira Cloud is to branch and capture the parent values for the field in created…

Thanks for that information, Chris. That type of field contains everything returned for the selection (the ID and value), so please try this: {{issue.Supplier.value.right(5)}}

I agree the user experience is not great for that approach, and... The fix to prevent clearing the field in an automation rule is to edit the description field like this: {{issue.description}} Here is my template for the field. Data to enter: TODO More data to enter: TODO This will add the template information after what…

Hi @Liam Spence -- Welcome to the Atlassian Community! You note that: If I have five dev teams all working on the same product, following the same release plan. Would the best way to set this up be using 1 project and having 5 components representing each dev team? From that I can guess you have a company-managed project…

Hi @Kima Atoyan -- Welcome to the Atlassian Community! Adding to what Vishwas notes, if you are using a Team-managed project, here is the suggestion to add card printing: https://jira.atlassian.com/browse/JSWCLOUD-17245 Kind regards, Bill

Hi @Nikki Zavadska _Appfire_ Yes, and...to what John notes: I tried a couple of experiments with automation rules and updating entity properties...I found neither the generic "issue updated" trigger fires nor is the change recorded in the issue history. And, I could not find any suggestions to add this capability in the…

Hi @Albert AG You could do this in two ways: * Using your existing fields, test for things which could be due and then use an advanced compare condition on the time relative to {{now}} I recommend using a field for the time rather than trying to extract it from the issue summary. * Rather than having a duetime field, have…

Hi @Chris Rose What is the type of your custom field? The functions you note operate on text values. So if the source field is numeric or a date/time, you may need to change to text first. Also for a question like this, it can help to include an image of your rule and audit log. Those may provide the community more context…

Hi, Bruno. Sorry, I do not know any free addons for this. And, I suggest searching in the marketplace as you may find one. A built-in work around is to use an automation rule to create a "default" value. One challenge with this approach is it makes issue creation a two-step thing: * create the issue, and the automation…

I just re-tried it and it worked for me. Perhaps try checking your field setup to see if the type / editor has been changed, as that might impact the contains operator. Otherwise I'd check with support as that should work for Jira Cloud.

Rebecca, I am glad to learn that worked for you. Please consider marking this question "answered" as that will help others find solutions faster. Thanks!

Thanks makes sense to me, Olli... Sub-tasks (although distinct issues) are "part of" their parent, and so have additional smart values which allow accessing down to the children (or up to the parent) directly within the rule. For all others (epics to children, and linked issues) automation has limited data about the…

Hi @Belen Rubalcaba This appears to be the expected behavior; there is a suggestion to improve this, which you may vote for/watch to see progress: https://jira.atlassian.com/browse/JRACLOUD-77167 A possible work-around would be to extract/replace mentioned accountId values for displayNames using a call to the REST…

Hi @Bruno Teles -- Welcome to the Atlassian Community! I do not believe that is possible yet with company-managed projects, as you describe. The Scrum project you note appears to be a team-managed project, and those allow setting default values at a project-level. Can you confirm if your Scrum project was team-managed?…

Hi @Brock Jolet There appears to be a newer (?) feature for lists which allows pulling distinct values: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/#list.distinct Given what is described and your use case, I expect you could use a Lookup Issues action to find issues meeting the criteria: has…

Hi @Rebecca Graf There is nothing built-in which allows configuring the "days in column" to use a different threshold/unit of measure. There may be a marketplace addon which helps with this. As an alternative, you could replace this feature with a custom field and automation rules. * disable the built-in feature * add a…

That is curious, and one of these things is probably defect: * if/else does not allow adding another condition component once inside the block from the component selector * a condition component can be dragged into an existing if/else block If #1 is the expected behavior and #2 (which you are using) is a defect, there…

Thanks, Bud. To exactly search for "Bug 1" you will need to escape the quotes like this: project = BSP AND issuetype = Bug AND description ~ "\"Bug 1\"" ORDER BY Key ASC

Well done; I am glad to learn you got this to work! The smart values are case-sensitive and spacing-sensitive, so when in doubt use the information in this how-to article to confirm the smart values: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ Also, I note in your rule that you are…

@Diogo Ribeiro did the support team give you a link to the public defect so we can follow its progress? Thanks!

Thanks for that information. You could do that with the out-of-the-box features of saved filters and a dashboard. * Create a JQL filter for your Project 1, returning the issues you want * Save the filter * Create a dashboard, and add the Two-Dimensional Filter Statistics Gadget * Select your Epic Link field as the y-axis…

My apologies as I thought you were using Automation for Jira (the Lite or Pro version). I am not using the Server/Data Center version and so did not recognize your tool, and instead you appear to be using something else to perform the automation. What are you using to create the automation?

Thanks, and in that case you can probably simplify your rule: * trigger: issue created * issue fields condition: issue type is sub-task * Note this is the simplest condition component and I think you were trying to use the if/else * action: edit issue field, for your custom field, and select to Copy From Parent from the…