Bill Sheboy Expert

Hi @glen_adams_bellmts_ca -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will…

Hi @Christopher.Brandel Would you please clarify what problem you are trying to solve? That is, "why do this?" Knowing that may help the community to offer better suggestions / alternatives. In the meantime... With Jira Cloud, issues such as a Story, Task, or Bug link to a parent Epic using the "parent" field. They do not…

Hi @Brian Adkins -- Welcome to the Atlassian Community! First thing, I have not tried what you are describing. With that out of the way... Have you tried using the parent with the issue key rather than the issue id: parent=TEST-1234 Kind regards, Bill

That may be the case, and I would still start with the vendor's suggestions. The reason I suggest that is some marketplace apps do not store their data in ways accessible to automation rules. The vendor will know what is possible.

Hi @David Jackson -- Welcome to the Atlassian Community! That is not possible with the built-in features of JQL filters as the data you show is calculated from the issue histories and sprint information only the reporting. There are some older REST API endpoints for the sprint reports, but I believe they are no longer…

Hi @Chasity Carmichael -- Welcome to the Atlassian Community! There are several open suggestions to fix this behavior, such as these two: https://jira.atlassian.com/browse/JRACLOUD-62865 https://jira.atlassian.com/browse/JRACLOUD-81633 You may watch / vote for them to see any progress, although one of them is quite old.…

Hi @Elif Alverson For support for that marketplace app, please contact the vendor through their marketplace information: https://marketplace.atlassian.com/apps/1211044/issue-templates-for-jira?hosting=cloud&tab=support Kind regards, Bill

Hi @Ahmed Yousif -- Welcome to the Atlassian Community! Adding to Marc's suggestion... That appears to be a cascading selection field, and so the JSON syntax is different: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Cascading-select-custom-field And...you may need to use…

Yikes! IMO, that seems like an extreme workaround to a UX design defect.

Hi @Victor Dulepov I do not believe that is possible for Jira Cloud, and here is a suggestion to hide / show that "Add a Comment" on the backlog view: https://jira.atlassian.com/browse/JSWCLOUD-23563 You could add an additional suggestion (or comment on that one) for the other views. Kind regards, Bill

Hi @lila To set or clear a built-in checkbox field for JPD, I believe the advanced edit with JSON is required, under More Options. For example, to set the field use the custom field ID and the value of 1: { "fields" : { "customfield_10120": 1 } } You wanted to conditionally set the field, based on a field in the Epic being…

That appears to be one of the re-interpretations of WSJF from Dean Leffingwell's frameworks. You could create an Atlassian Automation rule to perform the calculation, provided you have numeric values for all of the inputs. Or use a marketplace addon which can calculate dynamic fields. To get you started on creating your…

Next thing to try: check for a "glitched" rule. For some reason, rules can get broken by too many edit / publish cycles. I do not know the root cause for this, but the way to check is: * same rule* disable your rule * navigate to the rule list * return to the rule editor * enable your rule * try to make the edit and…

Hi @Hans Polder Currently, I am only using JSON plugins with Notepad++ to help with rule writing, expression validation. There have been improvements over time in the validation of rules during edit, such as these recent ones: *…

First a disclaimer: I am just another Jira user / community member. I have no internal knowledge of the mechanics of the automation engine or the design decisions used. My ideas / opinions are based on usage, observation, and what I see in the documentation. Next on the hardcoding and cloned issue order: with a dynamic…

This could be a browser hiccup, so perhaps try: * close all browsers, * open one back up, * clear the saved cache, * close the browser again, * open the browser, login, and try it again.

Hi @Michał First thing, as this is an older thread I recommend creating a new question, and perhaps including a link back to this one. That will ensure more community members see it to offer suggestions. When you post your question, please include images of your complete automation rule, the relevant trigger / actions /…

Hi @Hans Polder Regarding your question: That smart value that you used for the varEpicsInProgress variable, is that something that just flows out of your fingers, or is there some sort of standard/tool/format that you use? It's pretty prone to error I can imagine, just forgetting one character would break it. I write…

In my experience and observations, the items processed by such branches run in independent processes running in parallel and asynchronously. This likely helps with rule performance as the branch could contain conditions or actions with nondeterministic run times (e.g., Send Web Request), and so blocking is reduced. There…

Hi @Lisa Hauser -- Welcome to the Atlassian Community! Please try the date / time functions for plus[some unit of measure]() https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-plus-unit--- Assuming your "Actual Start Date" is a date / time custom field, and that is the correct smart…

Hi @a855031 -- Welcome to the Atlassian Community! By WSJF, do you mean weighted, shortest job first, as described originally by Donald Reinertsen and then re-interpreted by others? If not, what do you mean? And, what do you mean by "assign priority to my features"? Do you mean the Jira Priority field (e.g., High, Medium,…

Hi @Michael Labrecque-Jessen -- Welcome to the Atlassian Community! As Mikael described, there is no built-in way to do this. I looked and did not find an open suggestion for this feature in the public backlog, so you may want to add one. In the meantime... A possible, convoluted workaround which I have not tried is this:…

Hi @Nagashankar I recommend using the Lookup Issues action to gather the linked issues with JQL, and then use the list max and min functions on the date values, respectively: * https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues *…

Hi @Alex Young First things first: incomplete work carrying over after a sprint finishes is a symptom, hopefully leading to team discussion and improvement experimentation. As things improve, measuring any carryover could be halted as the measure is no longer needed / relevant. Back to your question... Measuring the "#…

Hi @Igor Titov Smart values are name, spacing, and case-sensitive. When an incorrect smart value is used, it evaluates to null. The smart value for the built-in "Due Date" field is {{issue.duedate}} although there appear to be several aliases for it in Jira Cloud. Please change to use this:…

Hi @Rupali Choudhari Are you doing this with an automation rule? If so, is the rule triggered on a change to the Affected Service field? In that case, you could try the {{fieldChange}} smart values to use only the added ids to replace the one for Last Affected…

Hi @d.kamposos Please post an image of the audit log details showing the rule execution. That may help provide more context for this symptom. Thanks! Until we see that... You could restructure your rule to only process when there are issues to update. For example... * trigger: scheduled with JQL to find CR issues without a…

Hi @Digvijay Singh Gehlot and @Hans Polder I agree with the suggestion to use a JQL branch for this scenario. The smart values and hierarchy may be different than the built-in assumptions for parent branching. Hans, I note you using the Lookup Issues action but then using different JQL in the branch. Did you intend that?…

When I type in (or paste in) as smart value expression, it does appear below the Reporter field, allowing it to be selected. Please try that again and do not select the dropdown list (arrow at that right) and it should work. Here is an example where I used a Created Variable to do this successfully:

Hi @SUVARNA Dixit As this is an older thread, I recommend creating a new question. That will ensure more people see it to offer suggestions. Until we see that... There are two built-in story point fields for Jira Cloud: * for Company-managed projects, the field is named "Story points" * for Team-managed projects, the field…