Bill Sheboy Expert

Let's please get very specific on the symptom. This is what you stated earlier: ...the rule runs and says success but the "result" field at the parent level gets cleared after I transition the sub task to drop rather than taking the last sub tasks "result" value. What exactly do you mean by "the last sub task"? Is this…

Would you please try writing this to the audit log and observe the results. If that is a CSV list of numbers, that will confirm we do not need the quotation marks for text. {{issue.customfield_11131.id}} And...I wonder if the extra spaces in your expression after the "if" cause problems, so try removing those also:…

Thanks for that information! Would you also please show an image of the details of the Edit Issue Fields action?

That is interesting, Josh... My understanding is the id attribute is a number field, but I wonder if equals() is doing some type casting. What if you treat it like text by wrapping the value in quotation marks? {{#if(equals(issue.customfield_11131.id,"13603"))}}<a href="https://www.google.com">Test</a>{{/}}

Awesome; I am glad to learn that helped!

This is one of those situations where Atlassian decided to implement non-standard formats for date and date/time fields. The fix is to force the field's format during the edit in the JSON to match the requested format. In this case, that would be jiraDate. Using my earlier example, we would add this: { "fields": {…

Would you please post an image of your complete rule in one image, and another of the edit action where the error is occurring? (You can capture the entire rule in one image using a scrolling capture, either with a browser addon or app.) That will help to see the full context of where the error is showing in the rule.…

Hi @Mimi Peters and @Trudy P Claspill That does not appear to be possible yet. I checked the v2 REST API edit metadata and that field was not listed as available for edits. Then looking in the developer community, I found posts from people trying to read or change restricted issues. It seems only Forge apps could do it,…

Hi @Kevin Bui Thanks for this valuable information! I have a suggestion and some questions about this change.... Would you please consider updating the table shown in your post as many will find it misleading? Currently, the limits you are showing for "Previous monthly limits" for Free and Standard licenses only applied to…

Hi @Yavuz Selim Parmaksiz I believe there are at least a couple of ways to do this: * slower, and always works: call a REST API function with a web request, and filter on the results to get the user and their accountId * faster, and may not work: assuming the user has previously been assigned to your field in an issue, you…

IMHO it seems there is sometimes less candor and clarity about changes to automation rules, documentation, and example usage cases. There are some exceptions, like the recent feedback and follow-ups for the new Lookup Table feature. And so regarding this article's question, "How much is too much automation", I would…

If you have no branches in your rule, you can rely upon the order issues are created. And then you can reference the {{createdIssues}} smart value to get() the correct one. Note this smart value is plural, as it refers to all issues created up to that point in the rule. The get() function is a zero-based list, and so the…

Yes, that is correct. What type of project are you using: company-managed or team-managed? If you are using company-managed, you could instead create swim lanes based on JQL for each person. And I wonder: if at the stand-up, 50 different people have 1 or more things in progress they are discussing, there may be larger…

As I am no longer at my prior employer, I cannot check my many test rules to find an example...And even if I could I do not know what would display if an action was removed. (Remember when you could drag branches inside of branches...and then you couldn't any longer?) I am confident I have answered a question or two about…

Hi @Kajal Mittal -- Welcome to the Atlassian Community! That is not possible. Jira boards only use the assignee field for that avatar-based filtering. A work-around for what you ask is to use Quick Filters for your board, adding one for each person. For example: assignee = Bill OR coassignee = Bill Kind regards, Bill

Hi @Josh.Updyke This appears to be a duplicate of your other question. Please close this one and look here for response. Thanks! https://community.atlassian.com/t5/Jira-Software-questions/Smart-Values-Lists-and-If-statements/qaq-p/2479094 Kind regards, Bill

Hi @Josh.Updyke Adding to Trudy's answer... The reasons your condition is not evaluating to "true" are that you are trying to use iteration syntax with the custom field, and the test is on id attribute without any condition, as Trudy described. Perhaps try this: {{#if(equals(issue.customfield_11131.id,13603))}}<a…

HI @Trudy P Claspill It appears that @Nadeem Zakir is using Jira Server, and not Jira Data Center or Jira Cloud. And so the action Lookup Issues is not available. Kind regards, Bill

Hi @Mary Mark I recall from another post the answer is, "no". Although if you post images your complete rule details the community may be able to suggest a work-around. The reason for this symptom appears to be {{from}} and {{fromString}} on the transition from "nothing" to the initially created issue are undefined. And so…

Hi @Shabaz Adding to the answers from Mohamed and Marc, you are currently dashboarding the open, active sprint. If in the future you needed to show more information, such as completed sprints and the open sprint on the dashboard, it is possible to create a saved filter for your complete sprint(s) and then use automation…

Hi @jaime.gilmartinez Adding to Trudy's answer... There are some things to consider for your scenario, so please decide what you want to do for at least these cases: * First thing: do you only care about the relative change in timeframes, or do you need to "remember" what were the dates of the original blocked item,…

Hi @Pooja Sree Adding to Mikael's answer, please look here to learn more about the impacts of those settings: https://support.atlassian.com/jira-cloud-administration/docs/manage-global-permissions/ Kind regards, Bill

Hi @Benjamin Peikes That is not possible at this time. There is a suggestion to make what appears on the Actions list be configurable, which you may watch/vote for here to see progress: https://jira.atlassian.com/browse/AUTO-635 Kind regards, Bill

Does your {{SalesLinie}} information in the branch source contain your counter values that you want in the cloned issue summary? Can you please show what you are using to set the summary in the clone issue action?

Hi @Nguyễn Thành Long When you use Lookup Issues to iterate over the issues, you start the iterator, access the issues, and then close the iterator. For example, {{#lookupIssues}} {{key}} - {{summary}} {{/}} But in your expression you have this at the beginning: <p>{{#lookupIssues}}{{/}}</p> And then reference the fields…

I just checked Wayback Machine to confirm my memory and those actions were documented and available as recently as the web capture on 10 June 2023: Complete Sprint, Create Sprint, and Start Sprint.

Thanks for that information! Remember you need to use the replaceAll() function, and not replace() when you want to use a regular expression. Next, your final JQL needs to have quotation marks around the string values, like this from your original question: project = TRX AND issuetype = Epic AND status not in (Cancelled)…

Do you have two different rules in your scenario? If so, that actions one rule performs cannot, by default, trigger other rules. This is intentional to prevent a run-away rule execution problem. When you intentionally want one rule's actions to trigger another, go to the "downstream" rule that will be triggered, view the…

Without seeing your complete, current rule...here are some ideas to try to help: Context and scope are key in a rule. If something is created inside of a branch or if/else condition it may not be visible to other parts of a rule. And, when you create a variable or a table in a rule, they are only available for that rule's…

Thanks, @Darryl Lee and this is puzzling... I am highly confident those actions have been present for years and so this appears to be an intentional and unhelpful change. The work-around may be to now call the REST API functions. My hypotheses are they are partitioning the actions (as you suggested) between license levels,…