Bill Sheboy Expert

Hi @Gary McDermott You describe a large team using Scrum, has some role-silos, has rework, which sometimes carries over work between sprints, and want to improve visibility of "total life span" to stakeholders. Perhaps first discuss this with the team in a retrospective, performing a 5-whys exercise to better understand…

Again I recommend asking your Jira site admin to check the global automation audit log to look for any recurring, scheduled rules. If this rule is not sending them, and it is a non-standard email, I suspect a rule is sending them from another scope / project.

Hi @Simon Chan Thanks to the team for continuing to improve automation rules! Here is my feedback on the changes... tl;dr: This new UX seems to target an audience of people new to creating rules rather than experienced rule writers, engineers, and Jira admins. I envision after less-experienced users become accustomed to…

I do not see a date/time stamp in the audit log you are showing. Are you stating that the email is sent long after the rule has run? And, your rule's scheduled trigger is daily only. This means it will run once per day, at the time when the rule was published, and not at a specific time of day. If you need the rule to run…

Hi @Caleb Park I recommend first confirming the smart value for your field, Delivery Date. Smart values are name, spacing, and case-sensitive. And they often do not match the displayed field name on the Jira pages. When an incorrect smart value is used, it will evaluate to null, and often fail silently with no errors in…

Hi @Markus Pilenvik Yes, and...to Trudy's answer: What you describe is fairly common for Scrum teams who also have production support responsibilities. Visibility is key for the added items. As Trudy describes, consider adding these issues to the sprint, including a label or priority value to reflect their urgency. And…

Hi @Gregory Kremer Yes, and...to what Laurie was wondering on the text functions did not work as expected: Context is important for automation rule questions. To help, please try to post an image of your entire rule, images of the relevant trigger / actions / conditions / branches, and of the audit log details. Those will…

Hi @Glenn_Riley1 Adding to Mikael's answer... This symptom can also happen when the issue is not fully loaded after the Issue Created trigger. The work-around for this known problem is to add a Re-fetch Issue action immediately after the trigger. And also: I note your rule is performing 4 different edits on the trigger…

Hi @Harry Brar -- Welcome to the Atlassian Community! Without seeing an image of your actual rule or the audit log details... I hypothesize your rule is using if-conditions and not if-else conditions for the different cases you note. And so the rule halts after the first one. Please try using the if-else condition. If that…

Hi @Vani Chukkaluru -- Welcome to the Atlassian Community! If I understand your question, you are describing two symptoms: * Issues are matching the JQL in scheduled trigger even though they should not * After the automation rule is disabled, the notification emails are still sent Regarding the first symptom, if you run…

Hi @aravind1516 Are you using Jira Server, Cloud, or Data Center version? If you are using Jira Server (as your post seems to indicate), please try using the bulk-handling feature of branches: https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html With that you could branch to the…

Yes, that is correct. There is a Send Web Request action which may call the REST API functions. Again, I suggest first checking the audit log to observe if it contains the version update information. Then try calling the REST API function from a browser to see if the data is present. That will save time before trying to…

For a team-managed project, it is very easy to switch between a Scrum and Kanban board...perhaps too easy: the methods a team uses often result from a discussion. Once you decide you want to switch from Scrum to Kanban, you may: * from the left side of the page's options, select Project Settings * select Features * and…

I believe what you describe is already in the sprint report. And...this has the smell of opportunities to improve backlog refinement, sprint planning, and / or team focus after starting the sprint. Sounds like valuable retrospective topics. Perhaps a cheap, and temporary, way to do this is with card colors on the Jira…

I recommend trying to create your rule; that will help work out the details. To get you started on creating your rule, please refer to these documentation and example sources: * https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation *…

First thing, I am neither working for a vendor partner nor have I done so... I suggest bringing those broken links to Atlassian's attention. And, the policy on using only a company email address for that marketplace indicator makes sense to me.

Hi @Roopa V -- Welcome to the Atlassian Community! Adding to the answers from others, you could use the Multiple Issue Events trigger. However, the specifics of whether this would / would not work for your scenario depend upon what you are trying to do. (e.g., I recall there are some edge cases where an issue create (or…

Hi @esnaremaussa No, there is not. As a work-around the rule could first call a REST API function with the id value to get the name and then use that. This would require using the Send Web Request action. If you want to try this, here are some references:…

Hi @Shruti Shrivastava -- Welcome to the Atlassian Community Which version of Jira are you using: Cloud, Server, or Data Center? The lookup table action is only available with the Cloud version at this time. Kind regards, Bill

Yes, and...please review these as well: https://community.atlassian.com/t5/App-Central/Atlassian-Community-online-guidelines-Marketplace-Solution/ba-p/689723 https://community.atlassian.com/t5/App-Central/Updates-on-App-Central-Kudos-badge-Lozenge-Privileges/td-p/2497837

Hi @Fernando Garcia When accessing a selection custom field, the value attribute may be used to access it. Otherwise the default attribute is returned, which is the id value of the selection. For example, to get the value the user sees, try this: {{issue.mySelectionField.value}} For your case, that would return either…

Hi @Marcel Rossouw First thing, I recommend discussing this behavior with the team and product owner. Changing the sprint scope (or the sizing for any issues currently in the sprint) is a concern for the entire scrum team. From what you describe, you would need either one or two rules to detect changes to either the Sprint…

Hi @Tom Haapanen Filtering by a vote field is not possible yet. Please see this other question for some work-arounds: https://community.atlassian.com/t5/Jira-Product-Discovery/Filter-by-votes/m-p/2386546 Kind regards, Bill

Thanks for clarifying, Emily. For team-managed projects, I believe the "+ Create Issue" feature is only available for a Kanban board, and not a Scrum one. Instead try using the Create button at the top of the page, setting the sprint value during the create. I hypothesize that design was done so people pause and consider…

This is where conditions will help, allowing you to test if the value is non-empty (or changed) before the copy. I added links to help explain how to do the specifics. Before that, we need to confirm the smart values for your custom fields. Smart values are name, spacing, and case-sensitive, and often do not exactly match…

I recommend you trying to create the rule, as that will make it more concrete to observe if it works as you expect. And then we can adjust if you run into problems. What do you think?

My apologies if I was unclear; I will try to clarify... In general, to copy a field value from the subtask to the parent issue, you would need 2-3 rules: * triggered on issue create, checking if the issue is a subtask, and then editing the parent * triggered on an update of your field, again checking if the issue is a…

Hi @jmweli Please try using the startAt and maxResults parameters with your call: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-user-search/#api-rest-api-3-user-search-get For example: yourJiraUrl/rest/api/3/user/search/?query=displayName%20!%3D%20bill&startAt=51 Kind regards, Bill

Hi @emily -- Welcome to the Atlassian Community! What is your type of project: Company-managed or Team-managed? You may find that information at the lower-left side of the page's expanding area If you hover your cursor over the column, does the "+ Create issue" appear? Do you have any swim lanes enabled for your board?…

Hi @Quinn Campbell You could do that triggered on either (or both) the subtask create or issue field update. Or on the issue transition if that is the point at which your required field needs to be filled. However...when there are multiple subtasks for an issue, how will you know which one should be used to update the…