Bill Sheboy Expert

Hi @Dan -- Welcome to the Atlassian Community! I just replicated that symptom, and this seems related to the recent Compass changes for components. I recommend working with your Jira Site Admin to submit a defect here: https://support.atlassian.com/contact/#/ As a workaround, please remove the component field from the…

Hi @John Conneely -- Welcome to the Atlassian Community! Adding to Walter's suggestions... Are those the advanced roadmap fields you are updating? If so, using the custom field id and advanced edit with JSON is required as they are not yet in the field dropdown lists for edits: https://jira.atlassian.com/browse/AUTO-1263…

Which REST API function are you calling for this message? Just to confirm, you send the message and it shows no errors AND does not set (or update) the field? When you checked the metadata with the example issue, did the values appear in the same structure as you expected?

Hi @Adam Abela What problem are you trying to solve? That is, "why do this?" Knowing that will help the community to offer better suggestions. Until we know that information... Although an automation rule could detect and copy some issue updates, it may not be possible to detect all changes. And even when a change can be…

Hi @[deleted] For a question like this, please post images of: * each complete automation rules (with one image per rule), * images of any relevant actions / conditions / branches, * images of the audit log details showing the rule execution, and * explain what is not working as expected. That solution approach requires…

Hi @Sascha Sturm -- Welcome to the Atlassian Community! Have you checked if you have any automation rules which may be adding the child issue values to the parent? Kind regards, Bill

Are you trying to check for label values of SEAP or ACH? If so, I believe your rule needs a different structure so it does not halt after the first condition test: * trigger: manual * branch: to current issue* condition: labels contains SEAP * action: clone issue...into "SF Event to API Proxy" * branch: to current issue*…

Hi @Sutanu Roy -- Welcome to the Atlassian Community! This is very old question / thread, and so I recommend creating a new question, perhaps adding a link back to this one. That will ensure the maximum number of people see it to offer ideas. When you post your question, include the image of your complete rule, the audit…

When trying to match this way, the exact case must be used. Please look at example issues and your status configurations to match the names. Again as an alternative, you could force the names to uppercase for comparisons: {{issue.subtasks.get(2).status.name.toUpperCase()}} 

Hi @kristina_soriano -- Welcome to the Atlassian Community! Adding to the suggestions from @Carlos Garcia Navarro When you clone the issue in the rule, have you tried directly setting the sprint id using advanced edit with JSON to override any cloning of the sprint field? That may allow using just one rule. Kind regards,…

Hi @mummareddy supriya Are you cloning the issue with the menu option for Clone or cloning in an automation rule? If cloning with an automation rule, please post images of your complete rule and the audit log details. That will provide context for the community to offer suggestions. When you post the images, please add…

Please note {{issue.subtasks.get(2).status.name}} contains "Closed" and you are comparing to "CLOSED", and so the comparisons do not match as they are case-sensitive. You could either change the condition case to match, or better still, force the smart value to a known case by adding toUpperCase() at the end:…

No, built-in sprint behavior does not do that. When you look at the global audit log for the site, what does it indicate happened for the sprint? https://support.atlassian.com/jira-cloud-administration/docs/audit-activities-in-jira-applications/

Hi @Antônio Rabello -- Welcome to the Atlassian Community! As that is a marketplace app, not from Atlassian, I recommend contacting the vendor for help with your question. Their support contact information should be on the marketplace page for the app. Kind regards, Bill

Hi @Moheeb Qupty Since that original question was written in June 2021, advanced branching and incoming webhook trigger were both added for Jira Cloud automation: * https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935 *…

Hi @Leena K -- Welcome to the Atlassian Community! 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…

Hi @McKenna Hogan -- Welcome to the Atlassian Community! What problem are you trying to solve? That is, "why do this"? Knowing that may help the community to offer better suggestions for that problem. Until we know that... I recommend first discussing this with your Jira Site Admin as you may already have Jira features /…

Hi @philipf For future reference in rule writing... Smart values are name, spacing, and case-sensitive, and they do not always match the displayed name on the issue views. When the wrong smart value is used, they collapse to null, and often show no errors in the audit log. To confirm you have the correct smart values for a…

Hi @Frank Leclerc _Decadis AG_ I believe that gadget is for JSM customers only. Have you see it installed without JSM? Thanks! Kind regards, Bill

Hi @Benjamin van Leeuwen Yes, that is possible. The rule could be triggered on sprint completion, and then the page could be added with the Create Confluence Page action or by calling REST API functions using the Send Web Request action. The first method would allow using a template. Please look here to learn more about…

Hi @Josh Allen The create issue and clone issue actions for automation require selecting the project, as you note. And, I recall there is currently no REST API clone issue function. Some possible workarounds are: * List of if / else clauses to name each project in the clone action (as you described) * Using the Send Web…

Hi @vincenzo.spatafora Without seeing your entire rule or audit log details, it is difficult to diagnose this. Please post images of both of those. Thanks! Until we see those... How do you know both of those conditions are true? Did you try writing the values to the audit log to confirm the values before the conditions?…

Hi @Renuka Mogal -- Welcome to the Atlassian Community! There are many community questions (and solutions) for this scenario, and there is even a built-in template in project automation rules. Please search for those to see examples. The variation for your rule is the Epic and child stories are in different Jira projects.…

Hi @Eran Roiter I do not believe there are built-in features for Jira Cloud to automatically close sprints. It can be done with automation rules or marketplace addons. Please contact your Jira Site Admin to check the system audit log as that includes the sprint-related events and may indicate what happened. Kind regards,…

Thanks for that suggestion, @Tanguy Crusson As JPD appears to be built upon team-managed internals, one tricky part is the JPD-project-specific fields, and copying and field values (other than things like Summary and Description) with automation rules. That may require use of advanced edit with JSON to correctly select…

Hi @Rohan Bharadwaj First thing, this is a community of users with similar interests, learning from and offering to help one another. It is not for "urgent" requests. If your company has urgent Atlassian tool support requests, please contact Atlassian support. However your request is about training material, and that does…

Are you using Jira Cloud, Server, or Data Center version? If using Jira Cloud, the Lookup Issues action supports all current issue fields, including Start date. And...the Epic Link field is sunsetting for linking Epics to their child issues in Jira Cloud. Instead please use the parent field. For the change of epic parent…

Ah, the syntax is incorrect with the placement of curly brackets. Please try this: {{issue.Status_Elapsed_ChkDate.diff(issue.Status_Start_Date).businessDays}}

As written, I would not expect that rule to update a Story when work is logged for a Subtask. The reason is the branch is to Epic (parent), and Subtasks do not have an Epic for a parent.

Hi @mummareddy supriya Rather than adding to this question with a new question, please create your own. That will help focus the conversation on solving your need. When you create your question, please include your Jira version, an image of your complete rule, and an image audit log details showing the rule execution.…