Bill Sheboy Expert

In that case, I recommend using Comments rather than changing the Description field. As each comment is added to a Task, branch to the parent Epic and add the same comment.

Hi @Enzo Soulan -- Welcome to the Atlassian Community! It is unlikely the community will be able to answer that question. Here is the open suggestion to add the other fields for Lookup Issues with Jira Data Center's automation rules. You may vote for / watch it to see progress.…

Hi @Sruthi Kumaran In the Scheduled Trigger in the rule editor, there is a link to learn more about CRON expressions, and on that linked page, it shows examples for the last weekday of the month. Please look there to learn more. Kind regards, Bill

Hi @Mohit Jain Would you please describe the problem you are trying to solve by doing these actions? That is, "why do this"? Knowing that may help the community to offer better alternatives than copying text across multiple different issues. Until we know that information... When editing a field such as Description with an…

You could perform multiple calls to Lookup Issues with different JQL, saving the counts in Created Variables, and using those in the message. This may be easier to read in the rule, but will run more slowly. Or...use one lookup with smart value, list filtering to get the issues you want from the Lookup Issues result, and…

Vincenzo, the answer is, "no, that is not possible with an unknown number of assignees". As Laurie already described, the feature allowing iteration over the distinct assignees does not exist in Jira Data Center automation rules. If you have a small number of users (less than 20 people), another workaround would be to test…

Hi @eric_asktia_com I do not believe that has been fixed: allowing customers to change the default product selections for new users. In my last role, we had a problem where new users were added to Jira Product Discovery (JPD) by default. The current solution is to ask your Jira site admin to contact Atlassian Support and…

Hi @Leslie Hubertus Thanks for this announcement. It appears your first link to the blog announcement is broken. Please update that one when you have a moment. Thanks, again! Kind regards, Bill

Hi @tyrone kimble Context is important for automation rule questions... Did you get this solution approach / rule from a template or help article? If so, please describe that. When does this problem happen: for all created issues, for cloned issues, etc.? And, please post an image of your complete automation rule, images…

Hi @Homesh Agarwal I recommend not using a bot for Jira questions like this; they cannot access and assess the context for your Jira site to provide correct answers. And so, the wrong date increment function was recommended. Please try this…

As Curt showed, please try the "implements" link type. For example, the JQL could be this, substituting in your project: project = yourNonJPDProject AND issueType = Epic AND issueLinkType = "implements"

Hi @Benjamin Baker I am glad to learn you found a workaround for your scenario, and... That approach will work when the following conditions apply: * The JQL statement has an ORDER BY statement, allowing the use of the last issue's data in the next query. In your case, the sort would be Key; probably ORDER BY Key DESC…

Hi @Cash Coyne Not from inside of a branch to the parent, however... I hypothesize you are branching to the parent to use its data to decide if the trigger issue should be updated. If so, you could instead use Lookup Issues to get the parent issue's data, and use that in smart value conditions to decide, and then the edit…

Thanks for that information, and I do not believe a rule triggered on Issue Created can solve this when there are potentially more than 100 issues involved. Do more than 100 issues have the same value for the specific Internal Study Name" when a new issue is created? In practice, how are that many links actually used:…

Hi @Theodora Weston -- Welcome to the Atlassian Community! When viewing an issue, look at the links and you will see the clone ones. At the right side of the row there is an X to remove the link. If you regularly clone the same issue(s) and do not want the clone links for those, an automation rule may be used to remove…

Hi @Steve_G I do not believe that is possible, and there are several open suggestions to add that capability, such as these linked below. You may vote for / watch it to see progress, although many of these quite old. (I found one created in 2006.) https://jira.atlassian.com/browse/JRACLOUD-10015…

Hi @Gunnar Engel Your teams have decided that Lisa's work capacity will be split between the teams, and so they are likely doing different work to help each team. That work would be on each teams' board only. And, the expected capacity Lisa contributes is impacted as well, certainly less than 50% for each team due to the…

Hi @Dana Weinbaum 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 @vincenzo.spatafora Adding to Laurie's suggestions... I believe the only workarounds at this time are checking the Atlassian Marketplace for an app or using a saved filter. There are two ways to do the saved filter approach: 1) Create a saved filter which returns the issues due in the next week which are assigned to the…

Hi, Scott. Automation rules run when something happens, they are not associated to a specific Jira issue. For example: * when an issue is created * when a specific issue field changes * when an issue transitions from / to a status * on a specific date / time schedule * ... You described something like this: GIVEN a task…

Successfully using automation rules requires learning and experimentation, and so I encourage you to try this and learn from the documentation. When one just uses rules provided by other they often are unable to maintain and improve them in the future. I will provide an outline which you may try implementing... * Earlier I…

Short answer: no. Most of that information is in the issue histories (unless one deletes issues), but it is difficult to access with built in features. The control chart can be used, as you noted. There are also Atlassian marketplace apps which can report on history data if you want to investigate those.

Hi @Allison Hoellrich Without seeing the specifics of your automation rule... There are various date / time functions that may be used to increment (or decrement) by a specific amount. Please look here to learn more: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ If that does not help,…

Oops...I just noticed you are using the Issue Created trigger, correct? It is possible for that trigger to fire so quickly that some data is not yet available to the rule, leading to unexpected results and occasionally rule errors. The fix is to always add the Re-fetch Issue action immediately after the Issue Created…

Hi @Anna Kirakosyan -- Welcome to the Atlassian Community! I do not feel there are any best practices: only better or worse ones based on a specific team's needs, context, and scale. That being noted... I have observed three ways of doing this for UI/UX teams I have supported: * embedded* UI/UX skilled people are dedicated…

Hi @Shaun Jeavons The approach to sum a field from Epics linked to an Idea is similar to your one to sum the values from the children of Epics to their parent. The differences include: * Ideas link to their "delivery items" with a different link than the parent / child relationship. Try experimenting with issue searches in…

Hi @Bjarne Huuck -- Welcome to the Atlassian Community! First thing, I am using Jira Cloud, not Data Center, and my suggestions are based on what I know about Jira generally. Please test with your site. With that out of the way... What do you want to do with these issue counts? For display only, you could use saved JQL…

Hi @ramnik malik What have you tried to solve this need? If you have created a rule and it is not working as expected, please post images of your complete rule, the audit log details, explain the field types involved, and explain what is not working as expected. Those will provide context for the community to offer…

Hi @Katrina Pambid What have you done thus far to solve this need? If you have created a rule and it is not working as expected, please post images of the complete rule, the audit log details, the edit issue action, and explain what does not work. These will provide context for the community to offer suggestions. If you…

Hi @Dave Furlani I suspect that one, or more, of the regular expression constructs you are using may not be supported. As the documentation states, with emphasis added by me: The underlying implementation is based on Java's Pattern class and uses Matcher.find() to find matches.…