Bill Sheboy Expert

Thanks for clarifying as this scenario is a bit more complicated as both the major and minor versions increment. The key is to check the minor version first and then increment as needed. Below is a full rule, which I quickly tested and so I'd recommend trying this in a test project first. After you are happy with it you…

Hi! First thing, a disclaimer: I have not tried adding a page from a rule before. That noted... Next, please try to respond in the same conversation thread. That will help when others are looking for answers in the future so they can distinguish different solution approaches. Thanks! Okay...have you tried hard-coding a…

Hi @Jerry Feng You are using Jira Server/Data Center correct? If so, that does not have Create Variable for temporary storage, as does Jira Cloud. Rather than store the token, could you just reference from the earlier REST API response and include that in your call to the chat REST API? Kind regards, Bill

Thanks, Stefan.

Hi @Maroline Johnson You can do that using an automation rule, triggered on version released, and create the new one by parsing the released version's name with text and math functions: * https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ *…

Hi @Hasan Zubairi -- Welcome to the Atlassian Community! What do you mean by "reporting" and by "in the last quarter"? For example, if you wanted to list the issues resolved in the last quarter (Oct - Dec 2022), you could use JQL to find them, substituting in your project name. project = myProjectName AND resolved >=…

Hi @Dave Armstrong If you remove your branch to Current Issue, you may then reference the trigger issue's summary when the subtask is created with either of these: {{issue.summary}} {{triggerIssue.summary}} Also of note: the Issue Created trigger and fire faster than the data is available to a rule, leading to problems.…

That is curious... I recommend working with your site admin as they can export the list of all users, including their account id, and then you can search that CSV file to find the user to investigate further. If it is not present, I would then work with your admin to submit a ticket to Atlassian Support to investigate this.

Hi @Ivanna -- Welcome to the Atlassian Community! Context is important for automation rules, so I suspect the reason your reference to just Reporter failed is there is no issue at that rule scope. If you believe it is something else, please create a new question (rather than adding to this one), posting images of your rule…

Hi @Danno Would you please post images of your complete rule and the audit log details showing the rule execution? Those may provide context for the community to offer suggestions. Thanks! Kind regards, Bill

Hi @Akash L Your query does not include anything about date, so age of the issues should not impact the results. When you look at items that do not match, but that you expect to be returned, do they in fact have all of the criteria from the query: project, fixVersion, and cycleName? Kind regards, Bill

Hi @vyanktesh_chandely Adding to Stephen's answer... If you find the conditions are still failing in your rule after the Issue Created trigger, that can happen because the rule fires too quickly. The fix for that is to add a Re-fetch Issue action immediately after the trigger. That will slow down the rule and reload the…

Hi @Johan Markström At the bottom of each of the automation documentation pages, it often lists longer examples, like this one for lists: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/#Combined-function-examples The {{#somelist}} starts an iterator to walk a list and the {{/}} closes the…

Hi @tehden33 Are you noting that you are adding other things (i.e. other versions) in the fixVersion field, to help manage other things than environment, and that those other things are released? * If so, what do those things represent and is there another way to indicate them other than versions, which are typically used…

Interesting... By the way: using that branch twice in the rule should not help...I would expect it to worsen the symptom you describe. The reason is that branches on one-and-only-one issue (e.g. branch to parent, current issue, etc.) get run in-line and so they complete before the rule proceeds with the next step. But…

In your second image where you appear to have removed completed issues, it could help to see variation in count by board column/status, but not cumulatively as that aspect has been removed. The completed items no longer overwhelm the result display. And as you note, the Jira "CFD" does not correctly preserve the y-axis…

Correct; when there is only one issue at a scope in a rule, things like {{issue.project}} and {{project}} are the same thing. For the original topic, I am stumped on how to proceed. I also tried what you show, and tried with match(), and with home-made name/value pairs, nested iterators, etc. Created variables do not…

Matt, after reading another posting I learned they have loosened the limits up a bit and so a single query/trigger can do up to 1000 issues, and the total for a rule (if that 1k referenced others) is 5000. There are other limits for processing time, but the 100 limit seems to be old info; sorry about that!…

Thanks, Alex. I recalled a limit on processing time and wondered about someone trying to run a cleanup on something with a long worklog thread...leading to lots of processing for the REST API calls. Definitely an edge case...and probably should trigger a question: why exactly would one do that to an issue? :^)

Hi @Rees, Ian First thing, when any columns/steps are removed from a CFD, particularly "completed" it is no longer a CFD, and so what you see is what I would expect. And I agree with you on the Jira interpretation of a CFD, as it has many challenges...often making it less useful when flow has anything beyond the basics of…

Thanks, @Alex Koxaras -Relational- I was following along with your answers to the other/question thread on this topic, and wondered about this approach also. What concerns would you have about this rule causing a SLA/limits violation for automation (execution time/duration) and so causing the rule to fail? Kind regards,…

Hi @Sara Palmitessa Is your question primarily that you cannot see the fields in the "issue in epic" and "subtasks" list when viewing the epic? If so, that is not possible with out-of-the-box features of Jira Cloud. Here are a couple of suggestions to make the columns configurable for that view, which you may vote…

Hi @Umar testing There is nothing built-in which can do that. In fact, several of the Jira features do not respect the site or project settings for working days (or non-working days as holidays). There are a couple of work-arounds for this, depending on the complexity of your working days definitions: * Work with your…

Hi @Piyush_Annadate What have you tried thus far to solve this? If you have a rule, please post images of your rule and the audit log details. Those will provide context for the community to help. Until we see those...I am unclear about your scenario... What problem are you trying to solve: the what and the why? What do…

Thanks for that information, Anton. I understand the concern about a backlog becoming "stale", with older requests never proceeding and stakeholders/requestors losing interest. One helpful practice is to be intentional about work intake and backlog refinement. When a product owner/analyst actively manages ideation and work…

Hi @Boldizsár Vermes First thing, the only reason you can see those project versions is that the trigger is Manual, and so you are actually operating on an issue with {{issue.project.versions}} My understanding is the stand-alone {{project}} smart value is only available with the project triggers. Next, the closest I was…

Hi @Jesse Redl Disclaimer that I am just another customer, trying to help... Here is an open suggestion to add epic reports for team-managed projects, which you may watch/vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-17914 Kind regards, Bill

Hi @keerthi Please check the audit log for your rule, as it is possible a rule like this could be running into one (or more) of the service limits for automation rules: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/ Kind regards, Bill

Hi @matthew_bache How many issues are you expecting in the result set? If it is less than 100 you may find the issues with an automation rule. You could run this rule whenever you need to know the issues, or even run it on a schedule (or other trigger). Such a rule could be: * trigger: let's use scheduled, but it could be…

Hi @Anton Garri Fagerbakk I am curious: what problem are you trying to solve by doing this? Specifically, what value does it provide to assign an issue to someone who asked for a thing to be done? Kind regards, Bill