Bill Sheboy Expert

Thank you for those images, and... First thing: as these rules have the same trigger, I recommend combining them and using and if / else condition for the different flows. Next, I cannot tell from what is shown: are you editing the GPBI-Project-Status value in one rule and expecting that to immediately have an impact on…

That is correct: when smart values are used in a JQL expression it cannot be validated in the rule editor. But if you have already tested your JQL outside of the editor with example values (e.g., using Filters > View All Issues), that should not matter: create your dynamic JQL in the rule, and then test your rule by…

Hi, and thanks for the update, @Janice and... I tried it and noted there is no "type" for this recognition (e.g., For going above and beyond), and instead shows "from profile hover card" when reviewing the ones I have given in the top-bar navigation. It appears it still counts against the 10 kudos total available per week.…

Let's assume the variable you created with the Claim Number is named varClaimNumber, and your field in the other issue is also called "Claim Number". The JQL inside of the rule could be this: project = CLM AND issueType = Claim AND resolution IS EMPTY AND status != Lead AND "Claim Number" = "{{varClaimNumber}}" Please try…

Hi @Brian Courtney -- Welcome to the Atlassian Community! I do not have one currently, and it should be straightforward to create... * First, add a custom field to record the CompletedInSprint. For a company-managed project, your Jira admin will need to add that. For a team-managed project, the project admin can do so. *…

Hi @Claim Guardian -- Welcome to the Atlassian Community! For a question like this, please include the following to provide context for the community to help: * what problem is your rule trying to solve; that is, "why do this" * your complete automation rule, in one single image * images of any relevant trigger, branches,…

Hi @Thomas A Yes, and...to Walter's suggestions: For automation-related questions, I recommend posting an image of your complete rule. That will provide context for comparison with the audit log details, and help the community offer better suggestions. Thanks! Kind regards, Bill

Hi @Mircea Craciun At this time, there is no way to configure a team-managed project's board to change when / how much is displayed in the "done" column: https://jira.atlassian.com/browse/JSWCLOUD-21257 As a workaround, you could create a Custom Filter to hide issues resolved / completed after a certain amount of time.…

Hi @Fernando Zeni Alvarenga -- Welcome to the Atlassian Community! When you want to update the just-created story based on the status of the linked issues, your have several options without branching to the linked issues: * use a related issues condition to check the linked issues * use smart value, list filtering on…

Hi @Josh Marsh I recall experimenting with {{index}} within iterators a few years ago, discovering it appears to be a just-in-time attribute of the list iterator and does not exist in a way which permits use in functions, filters, etc. A possible workaround is to expand the list into another variable with each index, and…

Please see my original reply for doing what you asked, as there is likely no need to check the issues to find the future sprints.

I was noting in the assignment of the Sprint to the created issue, and not in the filter for the trigger.

Hi @JUDY EDMONDS The roadmap is only one of the visualizations available in JPD, and there are several others. JPD provides one possible way to manage idea intake and product management (e.g., a portfolio) before selection and delivery begin. Please look here to learn…

Hi @Kim Alders Unfortunately, there are two story point fields in Jira Cloud, which may be displayed by their specific name or generically as "story points" in the UX: * For company-manage projects, the field is "Story points" * For team-managed projects, the field is "Story point estimate" Kind regards, Bill

I was answering the question you originally asked. You would need to review the interface to that call to know if it is correct based on what you are sending. From what I can observe... That rule uses a scheduled trigger with JQL. That means it will repeatedly make that call with Send Web Request. Is that what you wanted…

Hi @Tom Scoggin Using an automation rule and the REST API with the Send Web Request action, you could do that in a couple of steps: Gather the future sprints by filtering on the state: https://docs.atlassian.com/jira-software/REST/9.13.0/#agile/1.0/board/{boardId}/sprint-getAllSprints Update the filter by changing its JQL,…

Hi @Syed Nabeel Anwer For your scenario to access the maximum Due Date value, there are two possible approaches: * Use a branch with the bulk-handling feature and the plural {{issues}} smart value: https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html * Use the Send Web Request action…

Hi @Muhammad Moazzam Hassan I believe the lookup issues action for Jira Server / Data Center does not support the due date field yet: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 Kind regards, Bill

Hi @Yuqun -- Welcome to the Atlassian Community! First thing, and without knowing the specific "why" you want to automate moving issues to another project, I recommend not doing this with an automation rule. There is too much risk of an error / rule misuse causing a mess in your Jira site. With that disclaimer out of the…

Hi @wvacchiani Yes, bulk-update will change the same set of fields with the same values for all of the selected issues. To update with different values (or different fields) either: individual update calls are needed or you could use issue import via CSV (which would essentially be individual updates). Kind regards, Bill

Hi @Carl Alde -- Welcome to the Atlassian Community! Doing such an assignment with an automation rule is easy, although it will potentially consume much of your monthly automation usage allocation if your site has many such issues, given your Standard license level. If that happens, all of your rules will halt processing…

Hi @eric caprio The suggestion from @Shawn Doyle - ReleaseTEAM seems correct about the racetrack problem, and I hypothesize because the rule uses the Create Issue action (rather than the simpler Create Sub-tasks action), there is a logic error in the rule engine whereby the parent field is not always set before the…

What is the issue type hierarchy for your Jira site, in the global admin settings? The built-in, default hierarchy is this: * Epic* Story, Task, Bug* Sub-task That error seems to indicate that Epics are no longer parents of Tasks.

Please re-read my suggestion and that article. Your rule should look like this: * trigger: scheduled with no JQL included in the trigger * branch: on JQL to select your issues, and enable the bulk-handling option* action: send email, and it should reference the {{issues}} smart value. Please note that smart value is plural…

Hi @Harshad Prajapati -- Welcome to the Atlassian Community! As you are asking a new question; I recommend you create a new, separate question to help focus the conversation, and... For automation questions, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an…

Please show an image of the audit log details to help provide context. In the Create Issue action, please use {{sprint.id}} and not the name. That will ensure the correct sprint is used (and avoid any potential collisions). Finally, did you in fact create a sprint in that board exactly matching that regular expression at…

I have not used Slack in a while and I recommend checking their documentation on hyperlink formatting.

Hi @tatevikalaverdyan That may be done using the bulk-handling feature of branches, with the plural {{issues}} smart value: https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html Rather than using the branch on issues in sprint, please use the branch on JQL to include your test on the…

Hi @Nguyen Thanh Tien Depending upon the JQL in your Scheduled trigger, this is likely possible. You could remove the JQL from the trigger, just having it run every 5 minutes. Then use the Lookup Issues action to first check if there are issues for which to send notifications, and then branch over the distinct assignees to…

Hi @Jayanth That may not be possible in one rule. The reason is there could be timing / delay issues caused by transitioning the parent Story. Given the possibility of workflow or additional rule interaction, the event will not happen instantaneously. I recommend creating a second rule for detecting the Story transition…