Bill Sheboy Expert

Hi @Ben Weisman Are you asking about assigning the Project Lead to a custom user field? If so, there is nothing out-of-the-box to do that. Instead the rule would need to call the REST API with a web request to get the Project Lead's account ID, and then that could be assigned to the field. Here is some info if you want to…

Hi @jovanio_junior What problem are you trying to solve by doing this? Knowing that will help the community to offer suggestions. How are you trying to perform these steps: an automation rule, scripting addon, or something else? Knowing that will help the community to focus the suggestions they provide. Kind regards, Bill

Hi @Andrzej Hull When you have a question about an automation rule, please post images of your complete rule, the audit log details showing the execution, an explanation of what you expected to happen, and what you observed. That information will provide context for the community to help. Thanks! Without seeing your rule,…

Hi @Emma White Rather than adding story points to every issue/item on the boards, what do you think instead of having a conversation with the team about "what does done mean to us"? Doing that may help the team create/refine items which are valuable/releasable, and improve the ability to size requests to include all…

Hi @Jana Jäger If the automation rule you are trying is not working as expected, please consider posting images of your complete rule and the audit log details showing any errors. That may provide more context for the community to offer suggestions. Thanks! And, with two different cadences (3 months and 6 months) I suspect…

Hi @Tehmina Aslam That error in the audit log shows that the branch's JQL is not getting a key value, which can occur if the source issue was a Story or Task: checking one of those for {{issue.parent.Epic Link}} has no meaning as Epics do not have Epic Links. Please check again if your if/else logic is correctly handling…

In that case, I do not believe this is directly possible yet...according to this suggestion to add accessing project roles from within automation rules: https://codebarrel.atlassian.net/browse/AUT-279 One work-around would be to call the REST API with a web request from the rule to get the role information with this…

Andrew, if that edit is inside of the branch, then "current issue" refers to the branch issue and not the trigger issue. For your case you probably need to stick with the JSON edit...sorry I missed that earlier.

Hi, and thanks for that information. That indicates the rule is not even triggering. What is creating the issues: a person, another rule, an addon app, etc.? If another rule is creating the issue, please look at the details for your rule and enable the setting "Allow Rule Trigger". That will the issues created by the other…

Hi @Darryl Lee and @Christoph Kleinschmidt Please remember that branches on more than one thing/issue *always* run asynchronously and so this type of rule may never work with a branch. The reason is the parallel processing could result in re-fetching with the issue in an unknown state, and so repeatedly "walk over" its own…

Hi @Zachary Singh Where is the information about your "Project Manager Role" stored: an issue field, Jira Group, entity property, etc.? If it is any of those you could use an automation for Jira rule. To access a Jira Group you would need to call the REST API from the rule to get the user's account ID. For the others…

Hi @Liron Bdolach -- Welcome to the Atlassian Community! When you trigger these rules (with issue creates) what do you see in the audit log details? Please consider posting images of the audit logs as that may reveal what is happening. And also: there is a known issue with Jira Cloud and the Issue Created trigger where the…

I recommend editing your question and re-posting the screen image as it did not appear. Thanks!

Hi @Jonathan Nogueira You note using automation, and I wonder if you mean an Automation for Jira rule. If so, when you create the subtask in the rule, you could Branch on the Most Recently Created Issue and your email send could reference the fields in the subtask. Kind regards, Bill

Thanks for that information. I have not used ScriptRunner for many years, so let's see what other community members can suggest for using that addon.

Hi @Nash When I view rules from the project's context I only see the project's rules, and when I view rules from global settings (as a site admin) I see all rules. Would you please share a screen image showing what you see? That may indicate what is happening. Thanks! Kind regards, Bill

Hi @Alex G Short answer: sadly, that is not possible with the out-of-the-box dashboard gadgets. Longer answer: As the built-in gadgets have not apparently been updated in over 10 years, and there seems a push to use Confluence with addons rather than dashboards, you may want to investigate marketplace addon…

Thanks for that information, @cjohns I am still unclear what problem you would be solving with this use case, as there could be an interlocking tree of linked issues, and so that summed story points field may not be meaningful. It may be safer to only sum values for a parent issue to children, and I suggest considering…

Hi @Shankar Giridhar Vijayakumar -- Welcome to the Atlassian Community! To get the most people seeing your question: I recommend creating a new question, linking to this thread, adding images of your automation rule and the audit log details showing an execution that does not work as you expected, and explain the problem…

Thanks for those screen images, @Jan Šimek First thing: please try to keep to one thread in the discussions as that will help others see when there are multiple answers to solving your question. Thanks! Next, please consider looking for a browser addon to capture the full scrolling page. That can prevent getting pieces of…

Yup, context appears to be the issue. If you want the values from the trigger issue to be copied to the subtasks, use that info in the edit action. Otherwise when you do not specify the issue, it assumes "current issue" would would be the currently used subtask in the branch looping So in the edit, please try:…

Hi @David Hansen With out-of-the-box gadgets you could try the Wallboard Spacer gadget, and then rename it to your text. If you need a better, plain text gadget please take a look at the marketplace for addon apps. Kind regards, Bill

Thanks for that information, Rose! This appears to be related to the transition to use "parent" throughout the hierarchy, and move away from "Epic Link": https://community.developer.atlassian.com/t/deprecation-of-the-epic-link-parent-link-and-other-related-fields-in-rest-apis-and-webhooks/54048/78

Hi @Lesa Miller Short version: I do not believe that is possible yet. If you wrote the triggering user to the audit log, {{initiator.userName}} I believe you would find it blank. There is an open suggestion to add user-related fields to DevOps triggers for this use case you asked…

Hi @Amitava Mallick You may create an automation rule to do this, triggered on a change to the story points field. What have you tried thus far to solve this need? Here are some documentation and example references to help you get started: * https://www.atlassian.com/software/jira/guides/expand-jira/automation *…

Hi @Bill Bayer You have a couple of options on this need: * when multiple fields change, {{fieldChange}} is a list and can be processed as such with the iterator syntax * {{changelog}} also contains any possible changes, and so you could specifically reference your fields and ignore the ones which are null in the from/to…

Hi @cjohns -- Welcome to the Atlassian Community! If I understand your use case, for any linked issues, you want to sum the remaining (non-done) story points into a custom field...regardless of the issue type hierarchy. And, this means that the same story points could be summed in multiple different issues (due to…

Hi @Rose Lebel -- Welcome to the Atlassian Community! For a question like this, please consider posting images of the automation rule and the audit log details showing the error. Those may provide more context for the community to offer suggestions. Thanks! Kind regards, Bill

Hi @Sweeta Arya For a question like this on a marketplace vendor addon, you may want to contact their support team directly: https://marketplace.atlassian.com/apps/1213701/testrail-integration-for-jira?hosting=cloud&tab=support Kind regards, Bill

Hi @Jan Šimek Would you please provide more details about your use case/the problem you are trying to solve? For example, when there are specialized actions to take for each transition it may make sense to have separate automation rules...and when there is a common action for multiple transitions fewer rules could suffice.…