Bill Sheboy Expert

If you share some examples of your keywords and the corresponding components, I can probably help with that. For example... IF summary contains "blue" THEN add component "color".

Yup, that is where the JSON method helps. You can build a single expression to add them all at once. Without knowing your "decoder ring" to map the keyword values in the summary to the components, I expect the tricky part may be building the expression.

Oops, sorry: I forgot that the Create Issue action only supports adding one link at create time (due to a limitation in the REST API function). The work-around is to add one of your links with create, followed immediately by: * branch: to most recently created issue* action: edit issue to add the other link

If you want to update the trigger issue, I recommend changing the rule as follows: * trigger: issue created * action: re-fetch issue * action: lookup issues with JQL to load the issue you were instead branching to * advanced compare condition: Check if there was an issue found before proceeding.* first value:…

Hi @jan.ambroz Yes, that is possible...although perhaps not a good idea. (More on that later.) To do this your rule would use the Send Web Request action to call a Jira REST API function to gather all of the sprints, filter them to get your desired sprint's id, and update the issue. I have seen other posts trying this and…

Hi @Gregory Kremer 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 for the community to offer ideas.…

First thing, have you tried adding the Re-fetch Issue action to solve this? On to your questions... Yes, the {{triggerIssue}} smart value is available anywhere in the rule. (It is even available if there is no trigger issue!) For your second question, please note that context is important for rules: * {{triggerIssue}}…

Hi @JM Hoskinson -- Welcome to the Atlassian Community! There are several ways to solve this, and with the changes to the packaging model / limits for automation rules, combining rules seems a good…

Understood, but if you write that dynamic URL expression to the audit log, run your rule, and post the audit log details, it may reveal this is not formatting as expected. My guess is this is caused by one of two possibilities: * There is a known issue with the Issue Created trigger that it can fire so quickly that the…

Hi @Ahmed Saci Adding to Trudy's answer: A key thing for how you solve this is how subtasks are added: manually, in rules, or both. Seeing your rule and knowing that will help guide any suggestions. In the meantime: what problem are you trying to solve by having a unique identifier for each subtask, relative to their…

Sorry, what I meant was that would be 2 different links added. And so each smart value is used separately. And I agree: that ability to enter and select a smart value for some rule components is not in the documentation. I only found it by experimenting.

Hi @Lars Morten Nygaard I believe the way to see that now is to first enable the epic panel: ... menu > board settings > columns > epics on your board > select "Display in epic panel on the backlog" Only then will that slider appear at the bottom of the epics drop-down list from the backlog. I do not believe it shows from…

Hi @Jose Ramon Sagarna If you write that constructed URL to the audit log, what do you see? And, have you confirmed your request is set up correctly. Please see this article for an example: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 Kind regards,…

Hi @GGS -- 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 for…

I did some retesting and found several problems with the changelog not correctly detecting list field updates, including for the labels, custom field type. This reminded me of this open defect for the behavior: https://jira.atlassian.com/browse/JIRAAUTOSERVER-207 which also applies for Jira Cloud. Short answer: I believe…

Hi @Gema Ruiz In addition to the other answers provided... Using automation rules requires learning and experimentation. Often things we want to accomplish are not already defined in the templates provided by Atlassian. Instead we can build on those rules or create new ones to meet our needs. I encourage you to create a…

Hi @Piskorz Magdalena (BD/BTM-IC1) -- Welcome to the Atlassian Community! Your rule appears to be branching to the incorrect issue, and the lookup issues JQL is incorrect based on what you describe. Try changing your branch to Epic (parent), and changing the lookup JQL to: parent = {{issue.key}} That will return only the…

Hi @Malcolm Lisle -- Welcome to the Atlassian Community! Short answer: no. Longer answer: The closest thing to that for the out-of-the-box dashboard gadgets is the Sprint Health Gadget: https://confluence.atlassian.com/agile064/jira-agile-user-s-guide/using-the-jira-agile-gadgets/using-the-sprint-health-gadget That has a…

Hi @Hasmik Hovhannisyan What is not working as you expected? And...please add a write to the audit log after the trigger, including {{pullRequest.state}} as that may reveal if there is a mismatch with your condition test. Please post an image to the audit log details as that will provide some context for the rule execution.

Those results show there are no issues found. If you try that JQL stand-alone with View All Issues, adding the project information, what do you see? project = yourProjectName AND status = Done AND NOT status CHANGED AFTER -1d If there are no results, then there are no issues yet ready to transition. Also...please note the…

Thanks for that information, George. Those smart values showing the additions / deletions appear to be text, and not lists of values. Thus they need to be converted to lists for use in that action's add / delete of labels. Please try adding a split() function call to do that, such as this:…

Hi @Tomislav Tobijas What is the problem your customer is trying to solve by having that information? Knowing that may help the community to suggest additional solution approaches. Back to your question... Short answer to, "is this possible": maybe. My recommendation: If you really want to do this, consider doing it with a…

Are you using Jira Cloud, Server, or Data Center version? Would you please post an image of the audit log details, showing what happened when the rule executed? That may indicate what is happening. And...some tips: * For a rule like yours, the separate branch is not needed. Instead you may put that JQL in the scheduled…

As you want to create issues for a list of components, you may store that list in a created variable, and then use that later in the advanced branch, by using split() to create a list. That type of branch can use any smart value as a source. For example... * trigger: scheduled on your cadence * action: create variable, as…

Has this answered your question? If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. Thanks!

George, would you please confirm if you want the fields synched / duplicated between the Story to the Epic, or do you just want the additions / deletions copied (allowing the Epic to have more values than the Story)? And, please show images for the details of your edit issue action and the audit log details for the rule…

Thanks, and as I noted earlier: the changelog smart values only have data for the changed field(s), and so the trigger on Versions Ordered will not provide changelog data for your EpicLabels and StoryLabels custom fields. Your trigger would need to be on changes to StoryLabels to do what you asked.

FYI, please try to stay to one conversation thread. That will help others reading this thread in the future know if there are multiple solution approaches to try. Thanks! You note the field is cascading, yet the screen image seems to indicate something else. My understanding is the cascading fields can only be edited with…

Hi @George Tsemberlis First thing, when you describe the "EpicLabels" and "StoryLabels" fields, do you mean custom fields with those names or do you mean the built-in Labels field in the Epic and Story, respectively? Next, your rule is using a Field Value Changed trigger for the "Versions Ordered" field. That means any…

Please let me know if I miss any of the questions you asked... When creating (or editing) an issue, you may often type in a smart value expression. Type in (or paste in) the smart value, and it will appear below the field. You may then select it to use it. For your scenario of adding 6 issues, you want to add several…