Bill Sheboy Expert

I believe I have observed another loophole / condition whereby some appear to be searching for older questions (+6 months or older) which have no answers, particularly from new posters, welcoming them to the community, with a response along the lines of "has this been solved", "can you provide more details", or "you should…

Hi @Joanna Pietruszka -- Welcome to the Atlassian Community! No, I do not believe that is possible. If it was possible, any sprint's data could be changed at any time. That is, the "history" would not be what happened and when it did so. This would effectively make the reporting unreliable. Initially you noted "I had a…

Hi @Kiyotoshi Ichikawa -- Welcome to the Atlassian Community! First thing, I am using Jira Cloud and so my suggestions are based on what I know about automation rules, and not about Jira Server or Data Center versions. With that out of the way... I have not found any changelog information available with the Version related…

If you are trying to add the version from the trigger, please use the second one: {{version.name}} https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Fix-Versions

That should be okay also. I was noting that the "fromString" and "toString" would be relative to the project to-which-the-issue-was-moved. And so if the rule was project-scope, versus global, that is where the rule would trigger.

Sounds like that app is sort of "out-of-the-box" for ServiceNow, and not for Jira Cloud, correct? If so, does that have documentation to explain that symptom?

Hi @Justin Gong From an automation rule, that changelog information is only available with the Issue Moved trigger in the destination project. This would provide the information, if you wrote it to the log: {{issue.key}} was moved {{#changelog.project}}from "{{fromString}}" to "{{toString}}"{{/}} Kind regards, Bill

Hi @jmweli Is that integration for ServiceNow from a marketplace addon, and not built-into Jira Cloud? If so, you may want to check with the vendor to learn what they suggest. Kind regards, Bill

Hi @Nate Tarantino -- Welcome to the Atlassian Community! Would you please describe the steps you are following when the newly created issue is not linked? When I follow these steps, it does link to the idea: * while in a JPD project, select an Idea on a view (e.g., roadmap) * from the idea on the right side of the page,…

Before continuing I want to check something: is your intention to create one version in the other project or multiple versions, based on matching values? If it is creating multiple versions, I do not believe that is possible with automation rules, as branches cannot be nested and there is no REST API function to create…

In that case, I believe Jira Server automation can only loop over issues. Here is the suggestion to add advanced branching to both Server and Data Center versions in case you want to vote for / watch it for progress. https://jira.atlassian.com/browse/JIRAAUTOSERVER-749 I suppose an elaborate work-around would be to create…

This is an interesting, thinking back topic... During my time at a college-prep school, we were required to take the Scholastic Aptitude Tests (SATs) repeatedly until we got the maximum scores or time ran out before college started. And so I took them every six weeks for most of the year. (I never got the max on the…

Hi @Aaron Williams I recommend creating a new question, and linking back to this one. That will ensure more people see it to contribute, as only people following this older thread may see it. When you post your new question, please post an image of your complete automation rule, images of any relevant actions / conditions…

Thanks for that information, @lila When editing a field with that action, you may only use the field from the drop-down list or edit with JSON. You cannot do both in one edit action. Do you want to replace the value in the Fix Version field or to add values to it? * if replace, use the dropdown field method, and clear out…

Hi @mateus.oliveira The different versions of Jira have different versions of automation rule features...Does your version have the Advanced Branch type for rules, as described below? If so, that could be used.…

Hi @Rahul What have you done thus far to solve this need? If you are having trouble creating an automation rule, please post images of your rule and audit log details, and explain what is not working as you expect. If not, using automation rules successfully requires learning and experimentation. And this community is not…

Hi @Muhammad Moazzam Hassan Adding to Aron's answer... That is a built-in limit for the automation engine, which you may learn about here: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/ Based on the name of your automation rule, I suspect it is trying to make a cascading change to a date…

Awesome; I am glad to learn that helped! On your follow-up question...for this scenario, I do not believe there is a "proper" way to do this; just what makes sense for your team. Here are three ways to solve this, the first you are already using: (1) Using your solution if branching and if conditions, plus the re-fetch…

I am glad to learn that is working for you! Please consider marking this question that Trudy and I helped you with as "answered". That will help others in the community with similar needs find solutions faster. Thanks! And...yes, that query could find whichever issue types you search for. Assuming they all have the same…

Hi @Mikael Sandberg I believe these suggestions are related to what you are describing: * https://jira.atlassian.com/browse/AUTO-117 * https://jira.atlassian.com/browse/AUTO-592 * https://jira.atlassian.com/browse/AUTO-802 Kind regards, Bill

Let's confirm you are getting any issues back...After the Lookup Issues action, please write this to the audit log with the log action: lookup issues count: {{lookupIssues.size|0}} If that logs the count as 0, no issues where found and the JQL needs to be adjusted. With the on-going changes to sunset the Epic Link field,…

Greetings, and welcome to the Atlassian Community! Based on what you are describing, it seems you are adding the current total time rather than the time which was just logged and seen by the rule trigger. As shown here, the timeSpent smart value is the total…

Hi @Patrick Lewallen The reason only one value is persisting is because the later updates replace them. When rules run, they do not automatically update the information in the trigger issue; instead the rule "sees" what was present at the time the rule started. When an automation rule changes an issue, and you want those…

Hi @[deleted] Would you please post an image of your audit log details showing the rule execution? That may provide more context for this symptom. Thanks! In the meantime, I also wonder about the epic field changes and this one. Perhaps try writing the entire changelog (or just the values for Epic Link and parent) to the…

Hi @Maroof Ahmed Malik -- Welcome to the Atlassian Community! Depending on the structure of the automation rule, it may be possible to refer to the last created issue, and reference its dates. I do not recall if the {{createdIssue}} smart value works correctly outside of an if/else condition when the issue was created…

Awesome; I am glad to learn that helped :^)

Awesome; I am glad to learn that helped. Please consider marking this question as "answered"; that will help others in the community with a similar need find solutions faster. Thanks!

I am glad to learn that helped. For that second approach, prebuilding the JSON in a created variable can be challenging to get correct. When doing this, I will write the variable to the audit log (and skip the edit) until I know my testing is complete. Then I'll add the edit action.

Hi @Imre Antalfy Rather than using story points, has your team discussed using time-based estimation instead? That may better align with estimation at a sub-task level, could be forecast on "effort to complete" in time, be rolled up by person (or parent issue), and so help see the impact when the amount of work in progress…

Hi @Evan Fang -- Welcome to the Atlassian Community! The likely cause of that symptom is either the rule is using the incorrect smart value or looking for it in the wrong place in the data. Smart values are name, spacing, and case-sensitive, and when wrong one is used, they evaluate to null and often fail silently in…