Bill Sheboy Expert

Hi @David Tieman This may be a caching issue in the rule editor, or a defect from the recent changes to the Scheduled Trigger in the last few weeks. I looked in the public backlog and did not see this symptom. I recommend asking your Jira Site Admin to submit a defect for this here: https://support.atlassian.com/contact/#/…

Hi @Ashley Honeycutt Without seeing your complete rule(s)... I hypothesize you are using the Edit Issue action and selecting the Approvers field from the dropdown list to set the value. With the multiple rules triggering, the last one will "win" to set the value. Instead, please remove the Approvers field from the dropdown…

Hi @Patrick What is the scope of your rule: single-project, multiple-project, or global? A single-project scope rule may create (or clone) issues into other projects, but it cannot view or update them. And so a link to a newly created issue will not work. Try changing the scope to multiple-project. This will need to be…

Hi @Chris Smith-Hill -- Welcome to the Atlassian Community! Jira's Kanban boards can have a backlog view: * for company-managed projects, this is based on the mapping of the status values to the board columns * for team-managed projects, I believe it is always present as being "in the backlog" is independent of the status…

Hi @Akash Mukherjee -- Welcome to the Atlassian Community! When inside of the iterator for {{#lookupIssues}} ... {{/}} data, do not use the issue. prefix as the fields are coming from the lookup. For example: {{#lookupIssues}} {{key}} -- {{Story point estimate}} {{/}} Kind regards, Bill

Hi @Roger Mcgregor 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 provide context for the community to offer ideas.…

Hi @Dani Miles As this is an older thread, I recommend creating a new question, and perhaps adding a link to this one. That will ensure the maximum number of people see it to offer suggestions. When you do that, please include images of your complete rule, the actions / branches using that JQL, and of the audit log details…

Regarding the idea of having multiple status values in the last column on the Jira Scrum board, the first one to hit that column will show as "done" for burn-up / down. (The status category does not impact the burn for Jira's Scrum boards.) Has the team considered using a Jira dashboard with gadgets (and saved filters) to…

Hi @Sonora Braun -- Welcome to the Atlassian Community! If you read the other answers in this thread, you will find the solution: * remove the JQL from the trigger * use the JQL with the Lookup Issues action * then use the lookup results in your message Kind regards, Bill

Awesome; I am glad to learn that helps! Regarding your other questions... For documentation on Create Variable, this is all there is: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-variable And it does state the value is a string, but it does not suggest what to do when the value could…

There are several places in Jira where it removes any parentheses entered. In some cases, it appears to automagically reorder the clauses to match the original intent...some times not so much. The only workaround I have found is to ensure one orders the operators and clauses (perhaps adding extra ones) to ensure the…

Hi @Matthew Bliss I am seeing the symptom with a team-managed project, people field, with the single user restriction enabled, however... Once multiple values are added to the field and the values are saved (with the checkmark), only the first value saves, and then the field repeatedly prompts to search for users. But it…

I suspect many community members many offer opinions on your last question, and so there could be other ideas to consider. For me, I do not believe in "best practices"; instead I ponder "what are better (or worse) practices for a specific team's people, methods, and needs". What problem are you trying to solve by tracking…

Hello, community! Has anyone else noticed the notifications / bell has stopped working for the last day or so again? Selecting it times out, leading to this message: Unable to fetch new notifications Same symptom with different browsers and after cache-clearing actions. It was intermittent for the last couple of weeks but…

Hi @Daniil Lazarev -- Welcome to the Atlassian Community! What is the scope of your automation rule: single project, multiple-projects, or global? Single project-scope rules can create (or clone) issues into other projects, but they cannot view or edit the issues in other projects. That takes a multiple-projects or global…

Hi @Atlassian Service Team -- Welcome to the Atlassian Community! Short answer: I do not believe that is possible. I found some suggestions in the public backlog to track any users disabling notifications, and another to override user profile preferences (although that one was closed as "won't do".) A built-in workaround…

Hi @NUH For a question like this for diff() not working as expected, please provide the example date values, the result returned, and what you expected to happen. That will provide context for the community to offer better suggestions. Until we see those... The date / time function diff() only returns integer values in the…

Hi @Paulo Sebastião -- Welcome to that Atlassian Community! Although it would be interesting, and quite risky, if automation rules supported dynamic smart value expressions, they do not. What you could do instead is use your variable to build a regular expression and then use the match() function, passing that expression…

Hi @CEDRIC DEVAUX Created variables are text, and to use them in a function requiring a number they must be converted by adding asNumber. For example: {{issue.someDateField.plusDays(varSomeVariable.asNumber)}} Here are some other recommendations for the rule you show: * Perhaps write that created variable to the audit log…

Hi @Jan Walsh -- Welcome to the Atlassian Community! Adding to Hana's suggestions: To help learn more about the order of operations in JQL, please review this documentation and free training from Atlassian: https://support.atlassian.com/jira-software-cloud/docs/jql-keywords/…

Hi @Emna Elleuch Yes, that is possible. However, do you always want to do this, for every single Story created? Or, is there some set of conditions to decide when to also create the Epic? When an issue is created in a rule, the smart value {{createdIssue}} may be used to access its fields. And so after you clone your issue…

Hi @katharina.stech -- Welcome to the Atlassian Community! Yes, that is possible. To confirm, are both projects Company-managed or Team-managed projects? You may find this information by viewing the complete list of projects. For a rule to view and update issues in multiple projects, the rule needs to be global or…

Hi @Martina Hurtečáková How accurately do you need the field in the subtasks to be, regarding a match to the parent issue? That will determine how many automation rules you need, and which triggers they use. For example, you could have at least this many rules: * when a subtask is created, copy the field from the parent…

Hi @Simon Ma As John described, the time tracking fields are not supported for the Data Center version of the Lookup Issues action yet. Two possible workarounds for this depend upon what you want to do with the value(s): * Want to access / sum the fields for use in an email or message, and your rule does not need a branch…

I recall the guideline on the burn charts is based on the scope when the sprint starts, and so if all of the story points we set after sprint-start, the chart will be wrong. Regarding burning down values, is your final workflow status mapped to the right-most column of the board? That is how Jira Scrum board detect…

Hi @Cris Coffey -- Welcome to the Atlassian Community! Regarding story point fields... When team-managed projects (TMP) were added, Atlassian made a design choice to add a new field: "Story point estimate". The "Story points" field is the global one still used for company-managed projects (CMP). In the UX for TMPs, the…

Hi @jeremyn Are the parent issue's labels always-and-only a roll-up of the values from the child issues? If so, I recommend using Lookup Issues to gather the child issues' label values and replace the parent value completely, for any triggering events, when needed. The reason I suggest this is list and list-like fields…

Hi @Vivienne Clark -- Welcome to the Atlassian Community! That is not possible with the built-in features of JQL. Some possible workarounds are: * investigate the Atlassian Marketplace for addons to JQL which add that capability * investigate the Atlassian Marketplace for more advanced reporting options * create an…

Hi @Mohamed Alaa -- Welcome to the Atlassian Community! Without seeing the specifics of your rule, issue types, linking, and so on... Please try writing JQL which can identify an example, existing issue that was already created. That JQL could then be used with either a Related Issues Condition or the Lookup Issues action…

Hi @Dietrich Creating a specific, dynamic date for filtering is not possible with the built-in features of JQL. It could check using month adjustments to "now" or functions like startOfMonth(-1), etc.: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#startOfMonth-- Some of the workarounds you could try…