Bill Sheboy Expert

Hi @Maeneth I do not have much experience using SLAs with Jira automation, and I just read there are some known problems with triggering when you have lots of SLAs defined (and some time-trigger edge cases) https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#SLA-threshold-breached So a work-around…

HI @Chris Martin -- Welcome to the Atlassian Community! That type of reporting is not possible with the built-in features. You may be able to do that with a marketplace addon for JQL and/or reporting. You could also use the REST API to pull the changelogs (i.e. history) for issues and report in an external tool. Without…

Thanks for that information, @Frankie Sanchez Please also answer the questions Stephen and Trudy asked, as they may help clarify what is happening...particularly trying to manually create a Story in the same project where this rule is defined.

Thanks; I missed that part earlier. And it seems a better feature would be two "levels" rather than the one for "archive", as the current feature implies "this version no longer exists in production, and so cannot be assigned" versus "released, and exists in production so defects could be found".

Hi @Frankie Sanchez Is this for a company-managed or for a team-managed project? You can see that at the bottom of the page on the left-side expand area. Would you please post an image of what you are seeing in the rule? Kind regards, Bill

Hi @Neelesh PB Notifications are sent when the action occurs and based on the settings of the receiving person. If you want to send a notification at a specific timeframe, such as the Start Date set in a task, you could use an automation rule with a scheduled trigger, or a saved filter where people subscribe to it. Kind…

Hi @Eshita I do not believe all of those fields are available yet for automation rules, as described in this suggestion: https://jira.atlassian.com/browse/JIRAAUTOSERVER-135 To see which smart values are available in your instance/issues, please try this how-to…

Hi @Meghan Winters -- Welcome to the Atlassian Community! To clarify the symptom, do you mean all of the data entered on the form is not available in the rule or that the rule does not process all of the steps that you expect? * If it is the first one: the issue created trigger can fire so fast that the data is not yet…

Yes, and...here are a couple of open defects for that symptom for team-managed projects. You may watch/vote for them to see progress: https://jira.atlassian.com/browse/JSWCLOUD-21968 https://jira.atlassian.com/browse/JSWCLOUD-18461

Hi @Yakov Melman I do not believe there is a built-in permission to manage who can assign issues to a sprint, although there are permissions for all add/edit of issues. In my experience, this seems like a training/behavior issue for the team, and so making Jira "police" the behavior may not help. Instead an unintended…

Hi @Pedro G. Ferreira Do you mean: do not show the "released" versions in the drop-down list for version selection? If so, you can "archive" them after they are "released" (on the versions page) and they will not display in the drop-down lists. Kind regards, Bill

Thanks for that information, Renni. If you think about this like a data-centric analyst, when a customer asked to make a field required and there was existing data, the analyst would query, "how do you want to handle any currently empty, but now required, fields?" Otherwise the condition you noted with your original…

Hi @Dee Bernier In addition to Trudy's ideas... For such a large initiative, I recommend starting with a project liftoff/formation to create a user story map (or journey map) such as described by Jeff Patton in his writings. That will help with many of the early steps of ideation to small, releasable pieces for early value…

Hi @Spruha Shah -- Welcome to the Atlassian Community! First thing, I am using the cloud not server version, and so basing my suggestion on the documentation. Have you check from which board the sprint was created? When enabled, that option only shows the sprints created from the board which you are currently viewing.…

Please disregard, as that open issue appears to be with components and versions: https://jira.atlassian.com/browse/JIRAAUTOSERVER-207

I am puzzled how your rule worked as the {{project}} smart value is only available with the Project Created trigger, and not with scheduled and other triggers. Although I did find an old test rule I wrote which does something similar, and it no longer works; apparently something has changed for rules. The {{issue.project}}…

Hi, Trudy! Did you try that one with changelog? I recall a recent defect that some list/list-like fields were not working consistently for the changelogs in automation rules with {{fromString}} and {{toString}} Kind regards, Bill

Hi, Jack! Without seeing the result of the REST API call, I hypothesize possible causes could be: * there are indeed two, or more, fields with the same name at that scope, as you note * there is a trailing/leading space in the name of the field * the smart value is lowercase * and the less likely one...the field is somehow…

There are a few tools to do that, which you can search for online. As much of the syntax is based on automation rules, you may note find a perfect validator. One simple way to validate is to use a basic text editor which shows/highlights the matching quotes, brackets, etc. the expression. For example, the free app…

Hi @Tehmina Aslam Unfortunately, very few features of Jira appear to use the working days (or hours) configured for the site or at a project level. This includes ignoring any defined holidays for non-working days. Automation rule functions have this same limitation. One possible work-around is to first use plusDays…

Hi @Francesco Borgosano -- Welcome to the Atlassian Community! That error can occur when you have the incorrect smart value for the field, as it becomes an empty/null value in the expression. Smart values are name, spacing, and case-sensitive. Please use this how-to article to confirm the smart values for your fields.…

Thanks for that information. Perhaps try using the JQL function linkedIssues() as described below. With this you can specific the initiative, and optionally also the specific link type.…

A project-scope rule cannot transition (or make any edits) to issues in another project directly. You would need to use a global/multi-project scope rule to do so...and that will be impacted by the limits of your Jira Cloud license level. In general, I suspect such a rule would viable for a Premium license, as it can have…

Hi @Anand Babu Does your scheduled trigger have JQL (to gather issues) or is it just a schedule, without issues, to create a version daily? Kind regards, Bill

Hi @Ste Wright Just an FYI that rules like this no longer need to be global/multi-project scope. The clone and issue create actions allow creating issues in other projects from a project scope rule. The one limitation is going to/from company-managed to team-managed projects...due to the issue type and field changes. Kind…

Hi @Anthony Martinez Yes, you can do that with an automation for Jira rule, triggered on the issue create in "project A" and checking the labels before creating another issue in "project B". To get you started on creating your rule, please review this documentation and examples: *…

Hi @Yakov Melman Yes, that is possible...and...I suggest also having a conversation with the team about sprint planning and when/how to add things to an active sprint. And, changes to the sprint scope should be visible to all at the daily scrum (i.e. standup) so perhaps notification is not needed. If you still want a…

Hi @Jun Koo -- Welcome to the Atlassian Community! I believe the part you are missing is to split the result on spaces, and then add the commas. You could also use the asJsonObject() function, as described in the post you linked to. Kind regards, Bill

Hi @Moshe Mikanovsky As you appear to be doing this integration with Zapier, a marketplace addon app, I recommend working with your site admin and contacting their support team for assistance. Kind regards, Bill

Hi @Allen Culpepper I am curious: what did you hear back from the Atlassian Support team on this one? Thanks! Kind regards, Bill