Bill Sheboy Expert

Hi @Gustavo Soria With the two rules, are you expecting the actions on one rule to fire the other one? If so, please go to the dependent (second) rule, and check in the Detail options to select the Allow Rule Trigger. This setting allows one rule to lead to another one processing.

Thanks for that info, and... Your field looks like a number, but it is not one because it is in the list field. Let's try to convert it into a number before doing math on it: {{issue.created.withDayOfMonth(issue.Due Day.asNumber)}}

Hi, Adam! Thanks for the rule image. Do you mean that when you edit the Amount field within a rule, and then log it to the audit log, the updated value is not logged? If so, that functions as documented. The rule loads issue data at the moment of trigger, and when you change fields they are updated *in cloud storage*,…

Hi @Adam Dulberg First thing, I am just a user offering input, and not an Atlassian employee. With that out of the way... I did not find any suggestions in the public backlog for this idea, and you may add one if you wish. Update: I did find these two suggestions in the Code Barrel backlog (now part of Atlassian) *…

Hi @Kojo You are asking for something for your specific project and instance of Jira. Your Jira Admins will need to help you with that request, so please contact them for assistance. And, what you are asking may not make sense to them, so please be prepared to explain the problem you are trying to solve. It may not make…

If you write that to the audit log rather than try to change the field, does it work? If not, please try without the .value expression: {{issue.created.withDayOfMonth(issue.Due Day)}} And, would you please confirm if the Due Day custom field type is Numeric in the setup? Thanks!

Ah, now I see...Created Variables cannot be used a parameters in smart value functions (yet...) Have you tried to directly use that field value in the expression: {{issue.created.withDayOfMonth(issue.Due Day.value)}}

Sorry, no I do not. I am just a Jira user...trying to help the community when I can. :^)

Hi @Suvradip Paul I run into this error occasionally responding to questions. In my experience it occurs when I start responding, switch contexts to research and confirm my answer, and several minutes pass before I submit the reply. This seems normal and reasonable for a web-based application to handle as timeouts. I have…

Hi @Rodrigo Xavier I am unclear how your conditions would find issues created on weekends. You could try this instead with an advanced compare condition: * first value: {{issue.created.format("E")}} * condition: exactly matches regular expression * regular expression: (Sat|Sun) Best regards, Bill

Hi @Mark Sta Ana In your example, the thing you wanted to sort-by was always at the beginning of the summary. So why not just ORDER BY summary? If instead your substring is after the beginning, you would: * need some type of scripting addon; * extract the values into a custom field, and then sort; or * if you only need…

Thanks; that's what I thought you meant. :^) The challenge is {{issue.subtasks}} smart value cannot sort; it can only see the min/max/average... One work-around is to use JQL to get the subtasks in sorted order, yank out your due date, and then use it. Perhaps like this by expanding on your rule: * trigger: issue…

Hi @Lisa Stone -- Welcome to the Atlassian Community! I suspect this is possible, although it will be a more complicated solution. But first to confirm: what do you mean by the "NEXT sub-task due date"? Best regards, Bill

Hi @Nils Weinharra -- Welcome to the Atlassian Community! From your question, I infer you are using a company-managed project and that you have swim lanes set up on your board. Is this correct? If so, what are you selecting swimlanes on, and this may be the reason the issues are shown this way? Best regards, Bill

Hi @Brock Jolet -- Welcome to the Atlassian Community! First thing: there is a built-in field called Due Date, so I recommend using another name. The built-in field is what drives time ranges for things like roadmaps. Next, in your calculation ensure you fully specify the field smart value, such as:…

Hi @JD Lobue Yup, drag-n-drop only works when ordering by Rank. What type of project are you using? If it is company-managed, you could set up swim lanes by queries, checking the priority for what you need at the top. Then dragging will still work (within a lane). Best regards, Bill

Hi @Wojciech Cora How about using JQL, such as: project = myProject AND issuetype = Epic AND statusCategory = "In Progress" AND NOT status CHANGED AFTER -4w Please look here for more information on advanced JQL:…

Doug, I am glad that helped you. Please consider marking this question as "answered" in order to help others in the community find solutions faster. Thanks!

Thanks for clarifying! I suggest searching for common terms for those agile events in the marketplace to see what may be of interest to you: * refinement (formerly called "grooming"), sizing, planning poker, estimation, scope management, sprint goal, sprint planning, capacity planning, etc. *…

Hi! What you noted is confusing me a bit... Company-Managed projects (classic) have quick filters, and Team-Managed do not: https://support.atlassian.com/jira-software-cloud/docs/configure-quick-filters/ If you have a quick filter which is not working as you expect, consider posting that so the community can help give you…

Hi @Doug Robinson The smart value to return the week number for the current date/time: {{now.format("w")}} Best regards, Bill

Hi @Gustavo Soria -- Welcome to the Atlassian Community! If you decide to implement a solution with automation for Jira, that would require a global/multi-project rule for this use case. There are limits on the number of rule executions per month, based upon the license level. Please review this information to ensure your…

Hi @NAYANA Do you mean the information shown on Jira's interpretation of the control chart? If so please see this (emphasis below is from me): Cycle time is the time spent working on an issue — typically, the time taken from when work begins on an issue to when work is completed, but it also includes any other time spent…

Hi @Benjamin Peikes Yes, and to what Jack said with an example: * trigger... triggerIssue == current issue {{issue}} * condition... triggerIssue == current issue {{issue}} * branch... triggerIssue == current issue {{issue}}* stuff inside of branch... triggerIssue <> current issue {{issue}} as current comes from what the…

Hi @Paul Treadwell No, you would need a second rule, triggered on issue create and checking for an issue type of sub-task to automatically synch the child to the parent for that case. Best regards, Bill

Hi @Meriem Elheni -- Welcome to the Atlassian Community! Full disclosure: I am using the Cloud version, and... Based upon this comparison post, I expect that the answer to your question is "no", as the webhook features are not supported in the free Lite version:…

Hi @Puneet Khandelwal To help the community offer you ideas, would you please clarify what you mean by "Pre-planning and commitment ceremonies"? I do not recall those terms as agile events in scrum, which you appear to be using. Thanks, and best regards, Bill

Hi! I am not using any marketplace addons like that currently, so you could do a keyword search here and see what looks like it might help...and no doubt if there is a vendor watching this thread, they will suggest something. ;^) https://marketplace.atlassian.com/ For automation, here is some good information to start,…

Hi Igor, Other than a potential Y3K problem :^) I expect that if these two assumptions are valid: * you create the versions before you need them, and * the work is done *during the quarter for the release version* that... You could build the version name from the component and {{now}} with the text and date functions.…

I have had limited success for such tests with the related issues condition unless I explicitly stated the JQL. So you could try that with related issues, or use LookupIssues with JQL and check the return count greater than zero. The JQL would be something like: project = myProject AND (issueLinkType NOT IN ("depends on")…