Bill Sheboy Expert

You have created a rule which is manually triggered. And so you must manually start the rule, selecting it from the issue view under the Actions menu at the top-right side.

Hi @Amit Agrawal -- Welcome to the Atlassian Community! What is the type of your project: company-managed or team-managed? You may find this information at the lower-left side of the page expanding area. Company-managed projects use the "Story points" field and team-managed projects use the "Story point estimate"…

Hi @skuo Please try this to concatenate the values: Discovery - {{triggerIssue.summary}} Kind regards, Bill

Hi @ray.mcmanemin Your expression has the quotation mark inside of the {{^last}} expression and it should be before that, like this: {{#issue}}"{{labels}}"{{^last}},{{/}}{{/}} And...you may not need this, as the asJsonStringArray can do all that for you, including the enclosing brackets:…

Awesome; I am glad that helped! On the other question, I do not know. I did a quick test to Share a filter (using the button at the right-side of the view) with defined Private access, and it did not add the new user to permissions. So it seems those are distinct and different access features.

Hi @Kalyan Sattaluri First thing, is this for one project / team, or are many forgetting to "clean up their yard"? If it is one team this may be a training issue (until the process can be automated). Back to your question... I believe you have described the situation and limitations quite well! And, because Jira DC…

Hi @Chris D. -- Welcome to the Atlassian Community! FYI...the "For Similar Issue Description" branch was recently added for JSM projects, and "similar description" option needs to be enabled for the JSM instance for it to work. Although that branch type also appears in rules for Jira Software projects, it does nothing. Per…

Hi @Quinn Campbell Please take a look at this documentation page to learn about the functions available for date/time fields in automation rules: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ And if you look at the right side of that page near "Show more" you will find many other…

Hi @Phil Bustin Do the other users with whom the dashboard is shared have the same symptom? Have the saved filters used in the gadgets also been shared with those users (or a broader audience)? Kind regards, Bill

Hi @Jeroen Haesen What problem are you trying to solve by doing this? Specifically, "why do this"? The board shows the issues, and they already make visible what you ask by their placement on the board. Kind regards, Bill

Hi @Yee Ming Chew What type of project are you using: company-managed or team-managed? You may find that information at the bottom-left side of the page's expand area. And, would you please post an image of the audit log details showing the rule execution? That may help to explain what you are observing. Until we see…

Hi @Paula Lyon-Lee That is not possible with the built-in gadget. The Atlassian Marketplace may have a gadget for purchase to do so...or... A work-around would be to: * add a single-select, custom field to summarize/roll-up your status values * add an automation rule to set the custom field when the issues transition…

Hi @Emma Willcox Have you checked if any of the issues in the sprint have status values which are not mapped to the board? If so, that could be both the defect noted below...and a problem for the team as the issues will not be visible on the board. https://jira.atlassian.com/browse/JSWCLOUD-22951 Kind regards, Bill

That is different than your original question which Trudy helped with: summing up the issues which are linked with "implemented by". If you also want the subtasks they will either need to be linked also or modify your rule to account for the issue relationships. I suggest clarifying your scenario to help focus the ideas to…

Hi @Justus Hyytiäinen By design, automation rule branches which could be on more-than-one-thing (e.g. on JQL, Issues in Epic, etc.) are run in parallel and asynchronously. There is no guarantee of when the branch will complete...up to the very last step of the rule. As a result, you cannot rely upon a branch completing…

Hi @Rohith k Are your BA scrum board and Development board in the same Jira project, or in different ones? If they are in the same project... A Jira board is a view of the issues in the project based upon a saved filter. And so issues do not "move" from one board to another. Instead the issue fields are edited such that it…

Hi @Carola Tietz -- Welcome to the Atlassian Community! Is the End Date a custom field you have added? Out of the box, Jira uses the Start Date and Due Date fields for what I believe you are trying to manage. Once we have confirmed that, we can improve your rule a bit...such as: * trigger: the field (yet to be confirmed)…

Hi @Kent Chiu Adding to Trudy's answer... I recommend making the edits to Start Date and Due Date in one, single Edit Issue action. That will be faster and reduce the chance of rule errors (due to timing problems). After doing that, you could move the Lookup Issues action which Trudy suggests to above the new, single edit.…

Yvonne, is the rule not triggering or is it not processing because it stops due to a condition, etc.? You can check that by reviewing the audit log details. I just tried this with a Jira Cloud automation rule and it correctly triggered when work was logged for a subtask of a task.

Hi @Chuck Oleary Adding to Jack's suggestions...You note having over 100 different saved filters and need to update every 6 weeks. First thing, have you considered isolating the parts needing change in fewer filters so only one filter needs to change? For example... "PI Selection Filter", which is saved with an id, such as…

Hi @SUMUKHA HATWAR K N -- Welcome to the Atlassian Community! Adding to Rudy's answer and to confirm what you are observing... Please post images of your complete automation rule and of the audit log details showing the rule execution. Those will confirm we have a shared understanding of what you have tried. Thanks! Kind…

Hi @Yvonne and @Trudy P Claspill That expression appears to be missing a closing parenthesis for the divide() function call, and has extra spaces in it. Please try this: {{lookupIssues.Remaining Estimate.sum.divide(3600)}} And if that does not work, you can try the smart value, alias for the Remaining Estimate field:…

The other ways I can think to solve this are... * Export the issues, add the counter, and re-import the field for updates * Investigate marketplace apps which have scripted/counter fields * Build your own function outside of Jira to update the issues, and call that from a rule with Send Web Request

Hi @Hermance NDounga One advantage of using a manually triggered automation rule for this scenario is that trigger now allows adding user input fields at the time of rule execution, supplementing the information stored in the…

I am glad to learn it is working now. Looking at your rule, I wonder if some of the conditions/logic can be simplified... When checking a numeric expression (such as creating your variables), you can add a default value in cases where the result may be empty (i.e., null). For example with this... {{lookupIssues.size|0}}…

Hi @Prakash Paliwal -- Welcome to the Atlassian Community! Please look here to learn about the create issue, supported fields: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-post Kind regards, Bill

In that case, you may remove the asNumber conversions. Next, I notice you are trying to use that expression in a JQL action. That will not work as it is not valid JQL. What are you trying to test?

You are using the multi-select user syntax in the JSON, but you note the field is configured as single-select. For whatever the field type is, the syntaxes need to match.

The get() function for a list can only take a number for a parameter. It cannot take a smart value, either from a field or from a created variable. If you review my earlier posts, I described how to perform this type of search using a match() function and a dynamic search expresssion. When your rule is longer, you can try…

Hi @alecentalz If you want a clean slate for the cloned issue, you need to delete the worklogs. Please see this article from @Alex Koxaras -Relational- for how to do that in a rule: https://community.atlassian.com/t5/Jira-Software-articles/Delete-all-worklogs-from-an-issue-using-Jira-Automation-with/ba-p/2233207 Another…