Bill Sheboy Expert

Again, I recommend sticking with the parent field for this scenario. Please try creating a test rule with just what I provided to learn if that works as expected. It is possible the rule got "glitched", which can happen from too many edit / publish cycles, and so a new test rule may help to diagnose this. While using the…

Hi @Matthias Weidner -- Welcome to the Atlassian Community! There is another symptom to watch for: unsaved draft changes. We had a user make changes to an issue's Description, edit the field without saving, and move on to other things. Weeks later...they edited the issue again, saving their changes and walking over prior…

Hi @Maximilian Floß Based on your rule image, that cannot work for your scenario: * it is unclear what the initial branch is using as a source, as the entire rule is not in the image * a lookup issues action is inside the branch, is not used, and will not be available after a branch: things which are created inside of the…

As you saw in my response, the smart value you needed is {{issue.parent.summary}} rather than the fields you were using, and the values are case-sensitive. Checking case-sensitive values can be a brittle solution in rules as it relies on people not making mistakes. Instead consider using a Smart Values condition instead…

Hi @Jeremy Stafford The Epic Name field has essentially been sunset, and now the issue's Summary should be used. Are you trying to find any matches to "unplanned work" in either the Summary or Description fields when the issue type is an Epic? Does the case matter, as I believe that comparison type is case-sensitive for…

Hi @Blake Elliott There are several similar posts in the JPD community area with customers trying to use this new "date" field layout created by JPD team. Until they add support to automation and JQL for this field type... Others have been successful extracting the date needed (start or end) from the custom field using…

Interesting...Where are you storing the result of the concat() operation? I tried it updating the summary field and a tab was inserted. Updated: I just noticed you are doing this in an email.

Hi @Jason Chayer Yes, that is possible. The Send Email action in automation rules supports any email addresses, from the issue fields or typed in values. Kind regards, Bill

Hi @Jacqueline Arrindell -- Welcome to the Atlassian Community! Have you tried concatenating the code for tab instead, perhaps like this: concat("\u0009") Kind regards, Bill

Hi @Lucas Ferreira Has the team considered reviewing the built-in sprint report, such as during the retrospective, to see this information? That will show the additions / removals of scope for the sprint, and will not be impacted in the event someone changes the labels before they can be reviewed. That report is available…

Thank you for the additional information about your scenario. For a team-managed project, the setting for estimation type may be found here: left panel > Project Settings > Features > Estimation > once enabled, select the type of Story Points or Time.

Hi @Niklas Malmberg That post is for Jira Server / Data Center, which has different fields in some cases...like for parent apparently. The suggestion made earlier by @Valerie Knapp definitely works: * trigger: field change for Parent * condition: issue type is one of Sub-task (This condition type of "is one of" will help…

Hi @Maximilian Floß Advanced branching helps to loop over anything referenced from a smart value expression, such as from a lookup issues result. However, my understanding is the rule does not recognize the entity from the advanced branch as an issue within scope of the rule, and so actions like Edit Issue cannot act upon…

Hi @Jamila RAJA -- Welcome to the Atlassian Community! In addition to the other suggestions provided, I have a question: do you have one team or separate teams, with one team only working on the defects (i.e., bugs)? I ask this because you note using Kanban, and if there is one team doing all the work it may be better to…

Hi @Vitor Jr -- Welcome to the Atlassian Community! As that is a marketplace addon, and not built by Atlassian, I recommend contacting the vendor at their support location shown on the page you linked to. Kind regards, Bill

Hi @Jacques Dussault That is not possible with the out-of-the-box features of JQL. It only has some functions to help with relative comparisons, such as checking versions are in the earliest unreleased version, and so on: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#earliestUnreleasedVersion-- To…

Hi @Vishnu Vardhan Chenna Adding to Walter's answer (and for your future reference in rule writing)... Your create issue action is both setting the Parent (to an epic) and trying to use that parent's fields (e.g., Reporter) during the issue create. I have seen this work inconsistently, unpredictably setting the field to…

Hi @Quang Nguyen As you are trying to assign the newly created subtask, there are two ways to solve this: * After the issue is created, branch to Most Recently Created Issue to assign it, including your conditional logic inside of the branch * Assign the issue when it is created by setting the assignee field. Depending…

First, your regular expression in the match() is missing the closing quotation mark, which is causing that error. Here is the expression I suggested, and I added distinct at the end. That will handle cases where the same user is mentioned multiple times in the same comment. {{issue.comment.last.body.split("…

Awesome; I am glad to learn that helped! For follow-on questions, please consider if they are new-enough to be a separate question or modifications to this scenario. If different enough, you may want to post a new question, perhaps linking to this thread. That will help more people in the community see it to offer…

Hi @Trudy P Claspill This defect from the backlog seems related to what you are observing: https://jira.atlassian.com/browse/JRACLOUD-76147 Kind regards, Bill

Hi @Massiel Estevez -- Welcome to the Atlassian Community! Adding to Trudy's suggestions: Please also let us know if you are using a Team-managed project or a Company-managed project. You may find this information by looking at the lower-left side of the screen expanding area. The type of project is relevant because if…

You do not have names shown for your rules, so I will references them by the triggers used. And given the number of images posted and symptoms you are describing, I recommend trying to diagnose / fix one symptom at a time. Then we can proceed to the next one. For the rule triggered on transitioned to Done, you note it is…

Hi @Arvind First thing, using automation rules successfully requires learning and experimentation. This means reading documentation, trying to create rules and looking at the samples, adjusting as needed. When one just uses rules built by others without understanding them, they become difficult to maintain and improve. For…

Hi @Amish Khatri ( @ameesh khatri ) It appears you are using two different accounts, so I mentioned both. Have you confirmed the response body is both valid JSON and the automation rule recognizes it as a list of values? You can do this with a test, writing this expression to the audit log after the Send Web Request…

Hi @Eric Roetenberg That is not possible with the out-of-the-box features of Jira. There are several open suggestions to make the number of sprints configurable, such as this one from 2012, which you may watch or vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-6034 There are Atlassian Marketplace…

Hi @Meenakshi Manocha -- Welcome to the Atlassian Community! It seems you want to perform a calculation between two date fields to produce what you are calling a "lead time". That is not possible with the built-in features of JQL; it is not a SQL and has no ability to do this type of calculation as it is for issue…

Hi @Joshua Smith -- Welcome to the Atlassian Community! Please reread the original question and additional posts, as your suggestion does not meet the requested need. You suggest changing the filter to ORDER BY Priority DESC. But the question asked about ordering by Rank and Priority, while preserving the ability to…

I am not using the addon Team Files and am not familiar with it. You may want to contact the vendor's support team, or check their documentation, through their marketplace page.

Just to confirm when the Due Date does not appear for a Story in the active sprint: Is it not showing in the backlog, on the board, or both? Does that Story where the Due Date does not appear have any subtasks?