Bill Sheboy Expert

Well done! I recommend checking the performance of the expression, and if necessary, perhaps comparing that to use and() rather than nested conditionals to see if there is a difference. {{#=}} ( {{#webresponse.body.results}}…

Awesome; I am glad to learn that helped! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Hi @Adrian Szubert If you look at the markup for a mention with Jira Cloud, it looks like this: [~accountid:userAccountId] And so in your rule that clone / reuse such descriptions, the rule could replace those using text functions, such as replaceAll() with a regular…

Hi @Stephanie Bryant -- Welcome to the Atlassian Community! After some experimentation to confirm, I found .html rather than .htmlEncode gets the correct markup for passing to Confluence, and then follow that with jsonEncode for the Confluence update page endpoint:…

Hi @Giorgos Antonopoulos What problem are you trying to solve? That is, "why do this?" Knowing that may help the community to offer better suggestions. Until we know that... * All issues, including JPD Ideas, may use Issue Links to relate to one another * Additionally, Ideas have a special type of linking for connecting to…

As a suggestion when responding in the community, there is no need to copy everything from a prior post with your answers. Answering should be enough for the context to be clear. Thanks! Next thing: you describe different behaviors depending upon if all of the linked Tasks transitioned from different statuses (Ready for…

In an automation rule, smart values can be used in JQL. The expression I suggested is what will detect any duplicates.

I am glad to learn you have it working now. And when I tested, I did leave the rule actor as the default Automation for Jira user.

Hi @Jeff Ponce -- Welcome to the Atlassian Community! I believe the default connector allows quickly creating an issue like this: /jira create your issue summary That will open a dialog for additional fields / changes, or it could be immediately submitted. Will that one meet your needs? If not, have you searched the Slack…

The lookup issues result is a list of issues (0 up to 100 possible). And each issue has several list fields, such as Sprint, Fix Versions, etc. If we just looked at {{lookupIssues.sprint}} that would lead to the nested-list syntax I noted earlier. When nested-lists are viewed as text, it adds the square brackets I noted…

No, that method would not work because once inside the nested iterator, the other attributes are not accessible. How about still iterating at the higher scope, and filtering on the lower one using match()? {{#webresponse.body.results}} {{#if(attributes.values.key.match("(_TFT_)").size.gt(0)}} {{timeSpentSeconds}} {{/}}…

Hi @Stacey Jones -- Welcome to the Atlassian Community! Yes, and...to the suggestion from @Trudy P Claspill You could use a single branch to both the parent Story and the sibling sub-task for the "Code Review". Assuming the trigger issue is a subtask, the JQL for the branch would be this: key = {{triggerIssue.parent}} OR (…

Ah...it is trying to branch over subtasks of the trigger issue, but you want them to be from the source issue found by the lookup. In that case, change your branch type to JQL. If that variable is the key to your template story, the branch JQL could be this: parent = {{templateStory}} AND issueType = "Sub-task" Please…

Hi @Eloá -- Welcome to the Atlassian Community! To send one single message rather than one message per page, try removing the branch: * trigger: scheduled, with no CQL in the trigger * action: lookup pages with CQL, including checking for your deprecation information to exclude them * action: send the Slack message,…

Hi @Aaron Eden -- Welcome to the Atlassian Community! To which issue are you setting the parent of the new subtasks? From what you describe, it seems the parent is not selected or is setting to the trigger issue. If you want it to be a specific one, that key will need to be provided in the Clone Issue action. Kind regards,…

Again remember context: which issues are you selecting? If all of the issues are in the current sprint, you only need to check one issue: {{lookupIssues.first.sprint.endDate.max}} If instead this is an arbitrary list of issues, some with and some without sprint values, they all need to be merged first, and then a maximum…

Thank you for the additional information, @Jamshaid FYI - you describe the removal of duplication in the custom field using a ScriptRunner script. That could be enforced further in the advanced branch by using distinct: {{relatedCT.split(",").distinct}} You appear to be making the new issues unique by concatenating the…

FYI, after a quick test rule, this scenario is working for me with Jira Cloud, two company-managed, software projects, and a multiple-project scope rule. I was able to copy the Reporter from the issue directly. Who is creating the trigger issue: a person, another rule, or an external process? Are you changing the Reporter…

Hmmm...have you checked if there are multiple fields named Reporter set up for your site?

Let's try to set the value in the Reporter field directly with a smart value. Please enter this in the field: {{triggerIssue.reporter.accountId}} When it appears below the field. select it to use in the clone action.

Thanks for that information, John! What version of Jira are you using: Cloud, Server, or Data Center? And if your version is Cloud, what types of project are involved: company-managed or team-managed? What is the scope of your rule (in the details at the top): single-project, multiple-project, or global?

Hi @Vitalii Mural -- Welcome to the Atlassian Community! First thing: when do you want to create those issue pages in Confluence? If they are created as soon as an issue is added to a sprint, there could be quite a bit of "churn" when issues are added / removed from sprints. Thus requiring either manual cleanup or, with…

Just a heads up that something is "glitching" in the community for posts, and so you may see multiple posts for my same answer.

Hi @john.monteith First, this could be a timing problem caused by the Issue Created trigger. That one can fire so quickly that all data is not yet present, and so when you try to set the Reporter during the clone it doesn't work. To fix that, I recommend always adding the Re-fetch Issue action immediately after the Issue…

removing duplicate post

removing another duplicate post

removing the first duplicated post :^)

I am not using the Bitbucket REST API at this time, and I am not working in your Jira site / development environment to know its configuration. I recommend working with your team's engineers and your Jira Site Admin to implement this rule, step by step, and test it. I can provide this how-to article for calling a REST API…

Just to confirm, have you solved this question? And, please post an image where you are using JSON to set the Description in a way to add the checkboxes. Thanks!

Please post an image of your current, updated rule and the audit log details showing the rule execution. Thanks!