Bill Sheboy Expert

Hi @Tina Rusnak I do not have experience with Jira forms using dynamically populated data...although I suspect that capability may not be a built-in feature. Please consider creating a new question for this one; that will ensure the maximum number of people see it to offer suggestions and potentially any possible addon…

Before you do that... You can quickly test by using match function calls and only writing to the audit log. That will save time in getting the correct regular expressions before trying to set the field values.

Hi @Mateusz Bajorek -- Welcome to the Atlassian Community! Your update with the group parenthesis is correct, and you may escape the quotation marks if you do not want those in the result: {{issue.description.match("Application::\"(.*)\"")}} Also...do you expect any linefeeds / carriage returns on the description? If so,…

Hi @Randy Simes 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.…

Hi @Abdel Rahman -- Welcome to the Atlassian Community! No, I do not believe there is. You would need to pass all of the id (or value) items to select them. Kind regards, Bill

HI @Ganesh Kumar Vary Rather than using {{fieldChange.fromString}} you could use {{fieldChange.from}} to get the prior, selected id values, and then parse them to use advanced edit with JSON to set them back. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange--…

Hi @Mark Higgins Yes, and...to John's suggestion: Did you notice there are curly quotation marks (i.e. smart quotes) in the expression rather than the generic, straight ones? I do not believe the curly ones are supported in smart value expressions. Kind regards, Bill

I do not think so, and would recommend writing the constructed JSON to the audit log to check that approach prior to calling the REST API. My suggestion was based on some assumptions... * there is a multiple select, user field * there is a need to create one issue per selection * with each value from the user field set to…

Hi @Fabio Paglianti The original question is about summing for the child issues of an epic, not for summing the subtask's values. Please see the other responses for answers to that need. And looking at your post...for updating from the subtasks' sum, the JSON edit is not needed: the smart value expression may be entered…

Hi, Amy! If you are asking how to detect changes to the Fix Version field for the parent, and then copy the values to the child issues...there is a known defect with changelogs and list fields like that. The only way I know to do this is with a separate rule: * trigger: issue field updated for Fix Versions * condition:…

Hi! Earlier I noted the field type impacts detecting changes to a field. And although the Issue Field Updated or generic Issue Updated triggers usually work to detect the change, the specific values to check are determined by the field type: For a text, label, or date fields, this would work (substituting the correct smart…

I already suggested a solution approach: try using the changelog values: https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html#Jirasmartvaluesissues-changelogchangelog If that does not help, I recommend contacting your Jira Site Admin for assistance.

Hi @Colin The challenges to do this are: your rule is already using a branch, and I believe rules require adding the link as separate action after the issue create action. As your rule is already using the Send Web Request action, you could add one more to add the…

Hi @Jar Lady I suspect that depends on the actions you want to perform and the field types... All of the fields could be selected in the Field Value Changed trigger, and then followed by an if / else structure of conditions to check the changelog for differences for each field. However, some fields do not appear to…

To get the issues in the sprint, you may use the specific function for that or the issue search with JQL: https://developer.atlassian.com/cloud/jira/software/rest/api-group-sprint/#api-rest-agile-1-0-sprint-sprintid-issue-get…

Hi @Seikyo Cho You may get the specific sprint by id, as @Kalyan Sattaluri notes, or you may get all of the sprints for the board, filtering to the one(s) with the active state using the parameter: https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-boardid-sprint-get Kind…

Something else is doing that, and not the rule you are showing. Are you using the free license of Jira Cloud, or some other license level? Has anyone removed the Fix Version field from the issue edit views? Has anyone changed the configuration of the Resolve Issue permission in administration?

I was hoping to see the entire log entry, not just the error, for some context. Regardless... I wonder if the rule got "glitched", with something stored in the advanced edit section which is not displaying. Two ways to check that are: * Disable the rule, wait a few seconds, re-enable it, and re-test. If that does not…

Hi @Michael Ayers First, I note you have the function abs before the unit of measure days for the diff. Please try reordering those: {{now.diff(issue.customfield_10202).days.abs}} If that does not help...are you certain about the type of your custom field? Have you tried adding toDate to convert it:…

Hi @Colin Douglas -- Welcome to the Atlassian Community! When you noted this: However, now I find myself unable to modify the Fix version for any issue type within the project. Do you mean you cannot do so with an automation rule or when manually editing the field? If with an automation rule, please post an image of the…

Hi @Sean Hagans -- Welcome to the Atlassian Community! Would you please post an image of the audit log details from the rule execution, showing the error? Thanks! Kind regards, Bill

Hi @Bladimir Fernandez -- Welcome to the Atlassian Community! When you need to copy a field from the parent to the child issues, the rule needs to branch to the children first. For example: * trigger: some field changes * branch: to child issues (such as with JQL, subtasks, etc.)* action: edit issue, copying the field from…

Hi @Claire Parchem I suspect you have been fortunate the rule has worked up until now as it has a problem... When an Edit Issue action is used, it is based on the data at the time the rule started...unless the Re-fetch Issue action is included. Your rule uses two edits in a row, and so is possibly colliding or walking-over…

Yes, that will work. You could also try using the Issue Fields Condition as that will be simpler. I tried both with Jira Cloud and they worked, so it is likely the same for Data Center.

Hi @stuart lenox -- Welcome to the Atlassian Community! Short answer: One may write a rule to do this going forward, but not looking at prior time tracking. If this type of reporting is needed frequently, consider using a marketplace app for time tracking reporting. More information... The built-in reporting for time…

Hi @Pfohl Jason First thing, and in my opinion, it is generally a bad idea to change the issue type with an automation rule. There are many things to check when changing type, and this is why Jira has a specific feature for this: Move. Automation rules cannot make those checks (or show a dialog) to handle any problems.…

Sorry, I do not have answers for that. There is little documentation on the markdown features regarding field macros: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all My hypothesis is many Jira features have no REST API functions to access the data which configures the feature, and so automation…

Here is a simplified version of the instructions... * Your smart value is incorrect; that is why it is empty in the email body * Find an example Jira issue which has your field, SecondName * Look at your Jira URL in the browser * Open another browser tab, and enter this URL, replacing yourJiraUrl and yourIssueKey with your…

Hi @Phil Stebbings I recall some open defects where the Control Chart and Cumulative Flow Diagram do not work / display as expected when: * issues were imported from another site and the status id values were incorrect * the workflow had any status loops back to the same status If those apply, you may want to check with…

Carol, I was asking if the form field was stored in an issue field for use. I am not using JSM, but I do not believe form fields can be accessed from an automation rule's smart values.