Bill Sheboy Expert

Hi @Rune Rasmussen One way to do this with out-of-the-box features is to use an automation rules to extract the month value, for example into a label or custom field. And then you may filter on it easily. You will need two rules: one triggered on issue create and another in case the due date changes. For example to do this…

Hi @rcdpanjaitan How are you distinguishing teams? For example, with components, labels, etc. You can check the board filters to confirm this. Once you know how the teams are distinguished, you may add that to your query. Let's assume you are using components, then the query would be: project = myProjectName AND sprint IN…

Hi @Viorel Ioan Pacurar That error is indicating you are using conditions and actions which need issues, but the trigger doesn't provide any. The two ways to address this are: * Add JQL to your scheduled trigger to limit the impacted issues. This has the benefit of reducing the number of rule executions as it will only…

Hi @Julie Sgroi I do not believe there is a built-in way to do that. Issues can be exported, but there isn't a way to automate that. You could use an automation rule to send an email (or post a message, such as Slack) when the issue is moved to Done. I recommend investigating the marketplace for addon apps if you need the…

Hi @Steve Hooczko You could create automation for Jira rules such that when the values of those fields change, the sum is put in the other custom field. Please look here for examples and info to get you started creating the rule: * https://www.atlassian.com/software/jira/guides/expand-jira/automation *…

Please try this: project = myProjectNameA OR (project = myEpicProject1 AND issueType = Epic AND status IN ("use this status 1") ) OR (project = myEpicProject2 AND issueType = Epic AND status IN ("use this status 2") ) ORDER BY Rank ASC where myProjectNameA is your development team and the epics come from the other…

Hi @Dmytro Shaforost What have you tried thus far to solve this? I recommend using a branch or lookup issues to find the linked issue, save the assignee, and then you should be able to update the trigger issue. If you decide to use the lookup, you can directly use the value in the edit. * trigger: issue transition *…

Hi @Anthony Pugliese -- Welcome to the Atlassian Community! With built-in features, the answer is "yes" and "no" (if I am understanding your need correctly). Yes: For a company-managed project, you can limit the included epics by status with your board (and backlog) filter No: I suspect you also want the child issues for…

Hi @Amber Pacheco -- Welcome to the Atlassian Community! If you are using the built-in ordering mechanism, please try adding ORDER BY Rank ASC to your query to preserve the order. project = myProjectName ORDER BY Rank ASC Kind regards, Bill

Hi @Stuart Harris If you review that error, it says that the rule needs issue for the conditions and edit. A scheduled trigger can be used with or without JQL. Please write some JQL to identify the issues you want to check/update, and then add that to the trigger. With that JQL in the trigger, also note this option: * Only…

An idea to help: adjust for reviews that should happen during the upcoming week, giving you a window of time to respond. Use .format() to compare if the contract signed date (adjusted to this year) has a week matching the current week.

Hi @[deleted] If this rule works for you, I recommend using it; simple is better for a need like this. When I see use cases like this for a multi-year need, I ponder what Automation for Jira will even look like in 5 years, so making this overly complex may not be maintainable. One other thing to watch for, as this is for…

Hi @Doug Levitt Reading over your question and the response posts, I am wondering about the "processing" which this rule does. And what the need is, other than reporting in a specific order when completed. If only reporting order is needed, perhaps let issues "process" as they will, in any order, and then use a dashboard…

As comments could contain a variety of content (plain text and otherwise) there is no single type for a comment. You would need to check the body for any markup/tags indicating things like images or attachments.

If you can write JQL for "ready", then you could also add sprint IN futureSprints() to limit the results as you note.

I am not aware of an easy way to do this with out-of-the-box Jira. There is a REST API method that would allow updating the name: https://developer.atlassian.com/cloud/jira/software/rest/api-group-sprint/#api-agile-1-0-sprint-sprintid-post There might be a marketplace app to enable this, but that may not be worthwhile as…

@Addy Alago To clarify, team-managed (formerly Next-Gen) projects do not use Epic Link. They instead use Parent to link the epic to its child issues. So your edit may not work as you expect. Only company-managed projects use Epic Link. Thanks, Bill

Got it, and just to be clear: you are using Jira Cloud, correct? If so, then try this: * Take the JQL for your branch and instead use Lookup Issues with it * Remove the branch * Follow that with a if/else, and* Advanced compare condition on {{lookupIssues.size|0}} greater than 0 * Action to send the webrequest * Action to…

Hi @David Witcomb -- Welcome to the Atlassian Community! I recommend breaking your use case down into pieces, build it up, and that will help determine if this is possible. For example: * How are you doing checkboxes: with a checkbox field, a drop-down, or an addon? If with an addon, have you tested if an automation rule…

Hi @Olga Mocan -- Welcome to the Atlassian Community! You posted this question in the automation area, and I wonder if that is what you wanted. To just list/count the issues you could either use a JQL query or create a dashboard to show the issues returned by the query. If you needed this to occur repeatedly you may also…

Hi @David Kelman -- Welcome to the Atlassian Community! It appears you are running into an Boolean order of precedence issue, so let's see if we can shorten the query and make it easier. In general, it can help to structure your query with all of the common expressions first (i.e. true for all issues you want) and then add…

Hi @Evan Nixon You do not show your trigger's details, and I suspect that you have JQL in the trigger. Correct? If so, that is why this is running for each issue found by the trigger. The way to address that is to remove the JQL from the trigger and just run it on the time interval. Then use a condition to check for issue…

Hi @Natalia Chojnacka -- Welcome to the Atlassian Community! The issue created trigger may have timing issues, where the rule fires before the issue data is fully available. This can lead to rule conditions not matching. The work-around for this is to add a Re-fetch action immediately after your trigger, and before your…

Hi @ScrumPoint One of the challenges with the constraint limits for Jira boards is that they are not enforced; instead they provide a visual indicator of violating the min/max constraint. That is probably meant to help the team discuss the root cause of the symptom rather than have people believe the tool handles it.…

Hi @Mathilde Courtat Have you tried to write the ticket count to the audit log (log action) to see the value, as that may uncover what is happening? Also, would you please post an image of the audit log for your rule from an execution which does not work as you expect? Kind regards, Bill

Hi @Adrian Gonzalez Do you have the Automation for Jira addon from Atlassian? There are free (Lite) and paid (Pro) versions, and you may do what you ask with either. For example: * trigger: scheduled after X-days, perhaps with JQL to find the issues you want * condition: anything else you want to test first, prior to…

Hi @sebastien.devarennes -- Welcome to the Atlassian Community! What type of markdown are you trying to use? And, have you tried the same markdown in a simpler test rule which only creates a comment? I have noted that some of the markdown possible when entering fields like comment and description cannot be automated.…

Thanks for clarifying, Patrick. You may be able to create an automation rule to do that, probably with the addition of some custom fields. But first... * What is in your definition of ready? * Are you able to determine if an issue is "ready" using a JQL query? If you can write a query, perhaps you could instead use Card…

Hi @Hadas Hamerovv I am still a bit puzzled by what problem you are trying to solve. Anyway...you may want to consider using the field value changed trigger, checking for a change to your custom field. That may work more reliably as that transition may fire prior to the field change...leaving the data not yet set. Kind…

Yes, and... Smart values are not consistent between the UX and their spacing/capitalization. And sometimes you must use the custom field id value. You can always learn what automation is expecting for the smart value by finding an example Jira issue with your data, and then trying this how-to:…