Bill Sheboy Expert

Yup: for JQL and smart values, often the challenge is learning the correct name/format to use for a field.

Hi @Mart Postma For your step #3, a rule with a Scheduled Trigger could be used to check a field containing your date field (set in step #2). My assumption is that you are setting that field based upon being in a particular status: Review Next Month, Review Next Quarter, etc. Some references to help with your JQL are: *…

Hi @Dušan Stranatić -- Welcome to the Atlassian Community! One lesson here: do not create additional story point fields and expect the built-in reporting to work. The build-in reports, like the Velocity Chart, use the values in the built-in Story Points fields at moments in time using the issue history. And so even if the…

Hi @Alexander Ziegltrum Context is important for rules, to see where things are happening. Would you please post images of your complete rule, including details of the web request action? That may provide context for the correct smart value to use for your URL. Thanks! Kind regards, Bill

Hi @Martin Ibersperger -- Welcome to the Atlassian Community! For your original question, the trigger you used is Sprint Created, and so there are no issues provided to the rule. When you try to create an issue and reference the "trigger issue", there is none. Instead, you could assign the created issue to that sprint by…

Hi @Sebastian Pechhold I recommend not using bots to give you automation rule steps. The bot will not base an answer on your specific site information/configuration, and unless you ask the question with all site info possible it may be for another version of Jira (or assume certain addon tools). Instead consider quickly…

Awesome; I am glad to learn that helped!

Again without seeing your rule, I am guessing on the context of where in the rule you are trying to access these fields... Let's assume the trigger issue is a Story, and that has an Epic parent. For a company-managed project, the field you want is: {{triggerIssue.epic.description}} And for a team-managed project, epics are…

Hi @Marc Isikoff I recommend creating a new question for this one, and perhaps linking back to this thread. Otherwise only people following this older thread will see it to suggest ideas. And when you create that question, I recommend posting images of your complete rule, including details of the branch, and of the audit…

Answering your question "B" first: yes, when the rule runs the Lookup Table is created for use by the rule. (There are open suggestions to allow persisting those for later reuse by rules.) And for "A", it may help if you show an example of all possible values for that selection field. Seeing the values may help the…

Thanks for clarifying, Ian. Context is helpful for what you describe, and so which functions (e.g., create, read, update, etc.) are you trying to perform for the issue type involved? Looking at the specific REST API function documentation should indicate the supported fields.

If you use that expression in the request data is it working?

Hi @Patrizia Heinzl -- Welcome to the Atlassian Community! My understanding is the replace() function uses plain text and the replaceAll() function is the one which can use a regular expression: https://confluence.atlassian.com/automation/jira-smart-values-text-fields-993924863.html Please try using the replaceAll()…

Hi @Adam Rosenbaum -- Welcome to the Atlassian Community! Yes, and...to Jack's suggestions: When you create your rule, you may want to try using the new Lookup Tables feature, as that seems a good fit for your…

Hi @David Whitlock Please try doing that without the value attribute, as described here: https://confluence.atlassian.com/automation/advanced-field-editing-using-json-993924663.html { "fields": { "customfield_10004": 1 } } Kind regards, Bill

Hi @Ian Carlos Would you please clarify what problem you are trying to solve? That may help the community to offer suggestions. You describe using automation and the REST API functions. To learn the fields supported by the REST API for automation rules, please see this how-to…

Hi @[deleted] -- Welcome to the Atlassian Community! As @Laurie Sciutti already noted, until the team has completed sprints, none appear on the velocity chart unless: the estimation statistic is selected and the stories are estimated with that value. When you note that the reports show sprints by no data, what exactly are…

Hi @[deleted] Yes, and...to Jack's answers: Other customers have suggested making more information available to populate the user inputs for the manual trigger, such as described here: https://jira.atlassian.com/browse/AUTO-744 You may watch or vote for that suggestion to see progress. However for your scenario, the input…

Hi @Yuliia Yaremchuk Did you select the option "Enhance my board and backlog"? If so, the symptom you are observing may be related to this recent defect, which you can watch/vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-25768 Kind regards, Bill

Hi @Fernando Jordi de Lima Bueno -- Welcome to the Atlassian Community! Remember that a subtask's parent is the story, and the story's parent is the epic. When your rule uses the branch on Epic (parent) it is trying to reference the subtask, which is not correct. Instead please try using a JQL branch to update the epic,…

Hi @Danno What do you observe happening when you try this: the value is unformatted, is empty, something else? And, I noted that you typed this for the custom field name: "Expense Total (?)" Thus the smart value would be: {{issue."Expense Total (?)"}} First thing, is that a typo in the name? Next... Smart values are name,…

I think you have at least 2 options: Use that same REST API function which gets all issues in the epic, and then use smart value, list filtering and math functions to add up the story points. Please look here to learn about those…

Hi @Norbert Voßiek -- Welcome to the Atlassian Community! From my perspective, what you ask depends upon your team's interaction, maturity, agility, and development methods. Specifically, what does your team mean by these things? Short of everyone having expensive, immersive, remote-working hardware, and a well-crafted…

The URL provided by an issue only works for people who have Jira access for your site. Are you trying to provide this information to those without access?

Hi @Kalyan Sattaluri -- Welcome to the Atlassian Community! Once you have two results for the email address, you could convert that value to a list, and then grab the first one with either .first or .get(0) added to the end of the expression. However, that only works for linked email address values. If the source is…

Hi @Sarah Shoemaker -- Welcome to the Atlassian Community! First thing, please consider making a new question for something like this...and linking back to this original thread. Otherwise only the people following this older one will see your question to offer suggestions. Thanks! Back to your question... If you are using…

Oops, my bad: you are inside the iterator at that point for the lookup. Please us this to produce the list of comma-separated values inside of the {{#lookupIssues}} ... {{/}} structure. {{components.name}} 

Please separate the tests in the condition checking the Issue Type and Epic Name, such as I described earlier. * trigger... * condition: issue type is Epic * if/else condition for epic name equals Project Initialize* assign as needed * else/if condition for epic name equals Hardware* assign as needed * and so forth...

Great hikes, everyone! My favorite continues to be Carbon River Glacier at Mount Rainier. I have been going there for decades, although since the roads are now washed away the hike to it gets longer and longer. :^) Here is a picture of the approach crossing the river bed.

Hi @Mark Kurdyla Are you trying to add the name of the user who added an entry to "Issue Comments", based on the external source user's name? If so, are those people all Jira users, from which you could determine there name? If the user is making the field change in Jira, you could use: {{initiator.displayName}} for the…