Bill Sheboy Expert

Hi @Rachel Murray Just to confirm, do you mean that when you use a quick filter to remove the initiatives, they are still included in the 18 of the "12 of 18" shown? If so that is the built-in behavior...helping people see there are other issues not visible currently on the board due to filtering. If you meant something…

Hi @Geza Kukoda If Employee Name is the name of your field, please try this for the Lookup Issues JQL reporter = {{issue.Employee name.accountId}} And the "Validate query" option is grayed out because your JQL is based upon dynamic information the rule supplies at run-time, and it cannot be checked as the rule is defined.…

Hi @Chaitanya B For a question like this, please post images of your complete automation rule and of the audit log details showing the rule execution. That will provide context for the community to offer suggestions. Thanks! Kind regards, Bill

Here is the link: https://support.atlassian.com/contact/#/ If you are a site admin permission (or higher) you can submit the ticket; otherwise ask your site admin to do so and to add you to notifications. Once you hear back from them, please post what you learn to help the community. Thanks!

Thanks! Some field changes do not trigger rules/cannot be seen by that Issue Field trigger. Let's try this instead...please create a new test rule with these components: * trigger: issue updated * advanced compare condition: * first value: {{#changelog.score}}{{fromString}}{{/}} * condition: does not equal * second value:…

Hi @systems-intern You might need to convert the result of the format() operation to a number for the math to work, or store it in a created variable and then use it. To do it the first way, please try: {{now.withMonthOfYear(now.format("Q").asNumber.multiply(3)).endOfMonth.jiraDate}} Kind regards, Bill

Hi @Gaurav Dhuppar If I understand your use case, you have a parent issue with multiple subtasks, and there is an order of dependency between the subtasks. For example: parent => subtask A => subtask B => subtask C If that is correct, you would need to test with a if/else condition for each case individually to create the…

Thanks for that information, Todd. So you are manually setting the Score value and that change is not being detected, correct? Or do you mean there is also some addon named Backlog Prioritization which is helping to set the Score field?

Hi @Todd Iorio Do you have one automation rule setting the Score and another setting the Priority...and the second one is not triggering? If so, your two options to solve this are: * Look at the rule details section for the Priority setting rule, and enable the option "Allow Rule Trigger" * Combine the rules to perform the…

To use the Lookup Issues smart value, you first need to use the action for it. Something like: * trigger: issue transitioned * conditions: as needed to confirm you have your necessary conditions * action: lookup issues with JQL to get the linked issue with an assigned developer * advanced compare condition: to confirm…

Now that is interesting! My understanding was that linked issues (and parent links) only had access to some fields (e.g. key, summary, story points) and not custom fields...leading to the need to use a branch, lookup issues, etc. Otherwise a rule could potentially need to pull in a tree of issues' fields for the linkage…

Well done! I often reference that how-to article to confirm smart value names, spacing, capitalization. Now if you want to use that average you have created to do something like edit the trigger issue, the options to use that value are a bit limited: Once inside of the branch you can no longer use Edit Issue to change the…

I am glad to learn that helped, and sorry on my typo on the smart value name. I wish they were validated better prior to allowing save (or during entry): https://jira.atlassian.com/browse/JRACLOUD-75402 On that note, watch for the capitalization of smart values, such as {{lookupIssues}}. The spacing and capitalization are…

Quite an interesting topic! Yes, and...I wonder in conditions where bots often perform much of the initial sourcing/filtering of submitted resumes/cover letters, what would this look like? How would such a structure get the person noticed enough to get to the next step where they provide the qualitative storytelling,…

If both fields are the same type and it is not a time zone issue, you may want to submit a support ticket to Atlassian first. Just adding/subtracting the day to solve this may mask a different problem we are not noticing.

My apologies as I did note you were using the Server/Data Center version. Instead of Lookup Issues, the Server/Data Center version has a "bulk handling" option that can be used for a branch (or scheduled trigger with JQL). Just select that option and then use the {{issues}} smart value. Note that name is plural, indicating…

Hi @Julez The assignee has the "accountId" attribute and the user field set is looking for "id". So a work-around is to grab the field that is there, convert to the array, and then substitute the attribute name. Perhaps like this: {{assignee.asJsonObjectArray("accountId").replaceAll("accountId", "id")}} Kind regards, Bill

Hi @Patrick Kap -- Welcome to the Atlassian Community! Without knowing the specific problems you are trying to solve, the community may not be able to give you good suggestions that help. I recommend noting what information you want to see, why you want it, and then search the marketplace for addon apps to…

Hi @leodavesne What problem are you trying to solve? Knowing that may help the community to offer you suggestions. Making that re-ordering change would make Atlassian's interpretation of this diagram both no longer a CFD and prevent it from showing the things a CFD shows: arrival rate, departure rate (throughput), lead…

Hi @Bogdan Gorka For your question 1, you could try a couple of things: * This will most likely work: use a lookup issues action with JQL to find the desired linked issues (by type), and then use average as you did with the other list functions. * This may not work: try the smart value, list filtering functions to reduce…

Hmmm...You noted this: What I'd like to do is have automation that sets the appropriate NextVer when the task transitions to "Ready for Prod" based on the Component field. That seems to indicate you have Component values to indicate the product areas, and so the releases to use. For example, Calculator, Timesheet, DocFlow,…

Hi @Eric Roetenberg This could be a timing issue with the Issue Created trigger, where all of the data is not yet available at the moment the rule executes (e.g. the trigger issue's epic info). Please try adding a Re-fectch action immediately after the trigger. That will slow down the rule and re-load the data before…

Thanks for that information. I have seen some reports of intermittent errors like that. If it is consistently showing that error, please work with your site admin to submit a ticket to the Atlassian support team to see what they can find: https://support.atlassian.com/contact/#/

Hi @Julian First thing, I am not using Jira Service Desk. That out of the way... With two asynchronous things happening like this for Jira Cloud, I hypothesize there is no amount of Re-fetch actions that will guarantee this to work consistently. My recommendations if you need this behavior are: * check if forms have any…

Hi @Eric Roetenberg Yes, and...to Mark's answer...How often do you need to perform such a query? * Need one time: search for the epics with that reporter, grab their issue keys, and use that directly in a search. For example: Category != SAFe AND "Epic Link" IN (firstEpicKey, secondEpicKey) * Need often and have money to…

Hi @dwike_aprilia Are you trying to set the due date to the value from the issue that triggered the rule? If so, please use this for the edit: {{triggerIssue.duedate}} {{issue}} in a rule refers to the one that is "current" at that point in a rule. Within a branch that would be the issues from the branch rather than the…

Hi @Jacob Pines Yes, and...to Mark's answer: Two additional ideas... If you only wanted this to happen for subtasks, please add a condition after the trigger to check if the issueType is a subtask. Otherwise a team-managed project would cascade the value from stories up to epics also. Next, add a condition after the branch…

That is curious...as both are for the same custom field it does not appear to be a date/time to date conversion issue. I wonder are both for the same time zone? You could test that by forcing the value to your time zone before using it with convertToTimeZone()…

Hi @Joshua Dumas You wanted to update the trigger issue's Assignee with the linked issue's Developer, correct? If so... When you edit an issue, the "current" issue is the one impacted, and "current" depends on where you are in the rule. Inside of your branch, that would be the linked issue. If you want to edit the trigger…

Thanks for that information, and... It would appear there is work for the Story separate from the child Subtasks...which is why I considered that to be other work that is missing a Subtask. To do what you describe with story points, you would need a separate custom field for the total story points, although none of the…