Bill Sheboy Expert

Hi @metin.lamby I do not believe that is possible yet. You can create the page with an action, and I believe calling the REST API is needed to add content/make edits. https://support.atlassian.com/cloud-automation/docs/use-jira-automation-with-confluence/ Kind regards, Bill

I just did a quick look in the Automation Cloud and the old Code Barrel backlogs and did not see this symptom.

Shawn, in your rule which is just checking for the changes to QA subtasks, what are you trying to detect? For example, you noted not to proceed if the DEV subtasks were still not started or in progress. So perhaps add a separate condition for that after your QA subtask checks.

Hi @Karin_Gleichauf I find it unlikely the built-in automation rules could do this. HTML formatting could be quite complex, and so accurately striping it out and reformatting the comments would be challenging. Perhaps instead investigate other tools to remove the HTML before migrating the data into Jira. Kind regards, Bill

Hi @Ryan Hilliker I recall seeing some other posts related to this symptom, and the work-around was to use the id value for your status of "Done" instead of the status name. The causes seemed related to changes in team-managed project (formerly called next-gen) for the workflow and the in-progress changes to JQL. Kind…

Hi @Shawn Kaowili First thing: I suggest a team conversation to learn if the scenario you are describing (moving QA items before DEV items are completed) is valid. There may be a larger team process concern beyond the scope of the automation rules. Understanding that will help to know how to improve. After that...from what…

Hi @Alik Levin -- Welcome to the Atlassian Community! As you have already submitted a support request for this issue, I suggest contacting the Atlassian support team again for help. Just a reminder this is a community of Atlassian users forum, for users helping each other. It is not a channel to contact the Atlassian…

Hi @Kathy Banh -- Welcome to the Atlassian Community! There isn't anything built-in that can do that type of reporting. With your example chart, you could investigate the Atlassian Marketplace to investigate addon tools for purchase for this type of reporting. As another alternative, you could export the data for reporting…

Hi @Neil Armstrong -- Welcome to the Atlassian Community! Short answer: not with out-of-the-box Jira Cloud features Longer answer/work-arounds: Jira's JQL is not a SQL, and so does not have such features. And the reporting does not easily do this type of analysis: essentially looking for the absence of information (i.e. no…

Hi @Mikael Sandberg First thing, I am not using Lookup Objects in our instance...with that disclaimer covered... I wonder if you escape that for the exact string match if it would be accepted, such as with: "Department Name" = "\"Finance & Legal\"" Kind regards, Bill

Hi @Pfortmiller, Lee -- Welcome to the Atlassian Community! Automation rules run after the trigger (issue created), so if you want a template *before* you generally need either an addon from the marketplace or to set the field default for all. To add after with a rule, you can do that by referencing the description smart…

I agree, @Paul Newell ...especially when it can show multiple colors, when applicable, for a single issue.

Thanks for clarifying your scenario. Your rule is missing some branches to make it work, which is what is causing that error. * trigger: scheduled with no JQL * action: create a task * branch: on the most recently created issue (This will be the task created.)* action: create a sub-task * branch: on the most recently…

What we can see in your rule image is this: * trigger is scheduled (with no JQL) * create a task * create a sub-task for that issue * create another task * create another task * create another task In this case, only the sub-task from step #3 has a parent: the task created in step #2. If you want the others to have the…

Thanks, @Tanguy Crusson That seems different, and better than the standard issue flagging behavior for this portfolio context. We already added a Readiness field as select-type, and enabling the highlight seems to help. I am still trying to find (on a test project) where other highlighting is coming from; some other field…

Thanks, and...is there a source issue you want this rule to use (for the cloned data)? That is, where does that "parent link" come from?

Engaging partners Teams' problems we soon resolve Toward value alone

Hi @Bruna Junckes Sant Anna That error is indicating your rule actions are referencing issues and fields, but the trigger did not supply any issues. The fix depends upon what you want to do: * if you are creating new issues independent of other data, check the actions to remove an field references and smart values * if you…

Hello all, Yes, and...here is the open defect if you want to watch it for progress: https://jira.atlassian.com/browse/JRACLOUD-79371 Kind regards, Bill

Short answer: I recommend working with your site admin to submit a support ticket to Atlassian for this one, and to post back here what you learn: https://support.atlassian.com/contact/#/ Longer answer details... Thanks for trying that test rule. I am not using Advanced Roadmaps and so cannot test that one myself. After I…

Hi @Vincent Mutambuki { Mumo Systems } When recommending a marketplace vendor product, please ensure that you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines for Marketplace and Solution Partners…

As site admin, you should be able to create a global/multi project scope rule, and it may be as simple as: * trigger: version created (possibly adding some limits on the ones triggering this) * action: create version in the target project For this rule, ensure you do not enable the "Allow Rule Trigger" option, or this rule…

Hi @Amit Gandhi Thanks for the additional details on the use case. I do not believe that would be possible (or easily possible) to implement with out-of-the-box features, including automation rules. It would require more complex conditional and filtering logic than exists today. More complex work-arounds would be to…

I am not using any of the scripting addons, so perhaps someone else in the community can comment on that approach. For an automation rule, you could trigger on the issue create, or change of the field "A" value, and then set the field "B" using the built-in date increment functions:…

Thanks for that information, @Waqas Aleem As the organization is where you describe in their transition, you could also try: use story points with no changes, and add a "progress measure", based on your workflow, until it is no longer needed. That progress measure could be the percentage you mention, updated on issue…

Hi @Waqas Aleem I believe that is possible by various methods, including automation rules. However I am unclear why one would do this; it seems to redefine the meaning of "story points", particularly ignoring the ambiguity of relative sizing measures. What problem are you trying to solve? Knowing that may help the…

Did you try what I suggested for the user picker field for the edit action: * type in your smart value * the smart value will appear below the field * select that value below the field * it will now be used to populate the field for the edit

Hi @Preeti Yadav I believe you can do this with an automation for Jira rule, or with one of the scripting/calculated fields addons from the marketplace. Kind regards, Bill

Hi @Niklas Lampén -- Welcome to the Atlassian Community! Unfortunately, there are several different things called "team" in Jira. And I recall some other community posts that some of them are not supported by automation rules (because the REST API could not set them). Perhaps try a very simple rule to only set your team…

For your lookup issues JQL, you want to find the sibling subtasks of the same parent. This can work for that from inside of the branch. linkedIssue ={{issue.key}} AND issueType IN subTaskIssueTypes() If you want to ignore the Done issues, add that part to the JQL: linkedIssue ={{issue.key}} AND issueType IN…