Bill Sheboy Expert

Hi @lukasz.skurczynski -- Welcome to the Atlassian Community! First thing, is "End Date" a custom field or do you instead mean the "Due date" field? You are on the correct path with your second example: to increment a date value, use the plus functions in a…

Hi @Alex Relton Brown -- Welcome to the Atlassian Community! Without seeing your complete rule...I suspect you could use the match() function with a regular expression to search the response, producing a list of matches: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#match-- Then using…

Hi @Cash Coyne That is not supported for rules yet, and here are two related suggestions you may want to watch / vote for. One specifically notes adding the ability to email rule owners with the Send Email action. https://jira.atlassian.com/browse/AUTO-76 https://jira.atlassian.com/browse/AUTO-109 Kind regards, Bill

Hi @Natalia Wołoszyn -- Welcome to the Atlassian Community! I am puzzled by the workflow you describe, and so I wonder: If when the team refines a backlog item, and they apparently have some status specifically to indicate that (and which I suspect is not mapped to the Scrum board), why couldn't they then immediately move…

Hi @Harees Hussain -- Welcome to the Atlassian Community! That type of query is not possible with the out-of-the-box JQL. Other solution approaches depend upon how often you need to do this and your willingness to purchase marketplace addons: * need this often and able to buy addons* Investigate the Atlassian Marketplace…

Hi @Mahajan, Milind -- Welcome to the Atlassian Community! Yes, that is possible in one rule. An issue's parent key is available in a rule, and using that, you may use a JQL branch to access the other child issues of the same parent for any updates / synchronization. To get you started on creating your rule, please refer…

Hi @Shivam Singh -- Welcome to the Atlassian Community! What problem are you trying to solve? That is, why copy the comment? Knowing that may help the community to suggest better solutions. Thanks! Kind regards, Bill

Hi @Adam Sinko -- Welcome to the Atlassian Community! Saved filters are used for many different things in Jira, and so knowing the context is valuable. Additional conditions for components can be added, and... How are these filters you want to update used: for Jira boards, for dashboards, for scheduled subscriptions, etc.?…

Hi @Blacke조민기 -- Welcome to the Atlassian Community! From what you described, I wonder if your rule could: * be triggered on the sprint completion * check for any remaining / in progress issues * and update their priority, as needed. To get you started on creating your rule, please refer to these documentation and example…

Hi @van den Bergh, Marius, Vodacom (External) You may distinguish the inbound and outbound using the link types, depending on your rule structure and use of JQL or other actions. To validate these, I recommend first creating JQL outside the rule with an example issue and the issue search; once your JQL works as expected…

Hi @Purni The Issue Created trigger can fire so quickly that some of the issue data is not available to the rule when it starts. This will cause things like empty / incomplete fields when the rule runs. To determine if that is the cause, and to fix this symptom, please always add the Re-fetch Issue action immediately after…

Well, that took quite a bit of testing! First, some learnings: * The sprint smart value's startDate and endDate values cannot be used in rule functions; they apparently always collapse to null. Even converting to known date formats does not work. (A work-around was to save the values in created variables and then convert…

As Trudy asked earlier, would you please post an image of your complete rule, including the source of the Slack User id values, and an image of the audit log details showing the rule execution? Those may provide some context for what is happening. And would you please post an image showing the send Slack message example…

@James Smith -- I just saw your post in the other thread, and it appears you discovered the missing action to initialize the created variable to NULL. Is that correct? Thanks!

The values of variables for each iteration / loop of the branch on the AQL are definitely distinct. If the values overlap, that would be related to: * the AQL used for the branch (and so the objects returned), and / or * the smart value expression used to create the variable And so the double updates you note are likely…

Hi @James Smith Did you mean to post your response in this thread or another one? Thanks! Kind regards, Bill

Ralston, as the original poster, you can mark the question as answered by selecting the answer(s) that helped and marking it that way.

Ah...you posted this question in the Jira Software questions, and so may want to add this to the Trello questions instead: https://community.atlassian.com/t5/Trello/ct-p/trello

Hi @nat Are you using a marketplace addon / app for checklists? If so, the answer is probably "yes", and specifics for how to do this depend upon the app used. Here is the key...using automation to do this would add the template after the issue is created, not before. If you wanted to have the checklist template available…

Hi @Daniel Gauld I am seeing the same thing, and believe that is the default behavior: at the major interval breaks (in your case, "weeks") show the relevant timeframe (which be February for all the weeks in that month). At month boundaries, the month for the first day shown for the week is used. I hypothesize this is a…

Well done! All of those format modifiers return the date (or date / time) formatted as text. When you need to keep the value as a date (such as to set to another date field) leave the format off.

Hi @Joyce Wright -- Welcome to the Atlassian Community! Your last sentence describes the query well, and the key is to separate the parts: first check the things which are true for all issues, and then join together with OR the parts which vary. For example: this AND that AND anotherThing AND ( sometimesThis OR…

Hi @Melissa C I am using Jira Cloud, not Server, so please try this with your version: {{now.withNextDayOfWeek("FRI").minusDays(7)}} It is clunky but works...subject to time zone stuff and when you run the rule. Kind regards, Bill

Hi @Vanessa Formigoni Looking at that expression, it is unclear to me in what format you want to set the value for the diff: a number, text, etc. The diff value itself would be: {{issue.Start date.diff(issue.duedate).days}} Please adjust if the smart values in your Jira site are different. Kind regards, Bill

Hi @radhika Can you select your field from the dropdown list in the Issue Edit action? If so, try leaving the field empty to clear the value. If not available in the list and using advanced edit with JSON, try setting the value to null. Kind regards, Bill

Hi @sacha_rouzkhosh There are two challenges with your rule: Your rule edits the issue and then tries to reference the field which was just edited. The rule cannot "see" those changes for later rule steps, as it still contains the values at the time the rule started. To use the changes later in the rule, a Re-fetch Issue…

Hi @Uzmii As a work-around to add the subtasks to the existing bug issue types... Copy your rule, and change the trigger to Scheduled, with JQL for the bug to which you want to add issues. That rule can only process 100 issues at a time, and so the JQL must correctly detect when not to add more subtasks. You can run the…

Hi @Sanjivani Wayal For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, and an image of the audit log details showing the rule execution. Those will provide context for the community to offer ideas. Thanks! Until we see those... Rather…

Hi @Tomislav Tobijas First thing, a disclaimer: I am not using JSM or assets with rules, and so my suggestions are based on what I know about rules and not those products / features of Jira. Inside the branch, your rule appears to create a variable with the same name twice in a row, although I cannot see the details of the…

For variable name, use something to clarify the meaning. For example: * variable name: varEpicKey * smart value: {{createdIssue.key}} Then in the story creates, use this for the parent value: {{varEpicKey}}