Bill Sheboy Expert

Hi @Jessica Romero This is the formatting documentation for such fields: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all Please note many of the macros for fields like Description are not directly available. Instead, I believe one must call the REST API endpoints and use the Atlassian Document…

It appears you always want to increment the year, and so try pasting this directly in the field with the edit action: {{issue.customfield_10187.plusYears(1)}} That will appear below the field in the Edit Issue action, and then it may be selected for use.

Thanks for answering, @Trudy P Claspill :^)

Hi @Heather Hanselmann -- Welcome to the Atlassian Community! Short answer: you will need another rule for that, or to create the issues using the REST API and the Send Web Request action. By default, when an issue is cloned it sets to the initial status in the workflow. And changing the status is different from other…

Hi @Lucas Ferreira There is no way to alter the built-in behavior, and there are several open suggestions to make flagging more configurable. Here is an example one: https://jira.atlassian.com/browse/JSWCLOUD-2268 As a workaround, you may use an automation rule with a manual trigger and user inputs. For example: * trigger:…

Hi @Shiva Kumar Hiremath The Delay() action would have no impact on the symptom / scenario the question describes, and... The Delay() action is only available for Jira Cloud with the Premium and Enterprise license levels. This question is for Jira Data Center.…

Smart values (including functions) are name, spacing, and case-sensitive. There are several errors in your Create Variable action for varmyDate and other steps, and so I suspect the rule is comparing null and null in the condition. That could be checked with audit log writes for the variables and by reviewing the date /…

Awesome; I am glad to learn that helped! To find the correct smart value / custom field id for the "Need by Date" field, please try using this how-to article with an example issue: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ The basic idea is to use a browser tab to call the REST…

First thing, please try to stay with one thread when responding. That will help people reading this question in the future know if there are multiple solution approaches to try. Thanks! Your expression has unnecessary parentheses inside. It should be like this, correcting the case of the smart value: {{issue.Start date}}…

Thank you for that information. Regarding link direction, the rule only triggers one time when two issues are linked, not once for each issue. If your link could be added from either issue (by choosing the relevant direction), you would need an if / else block to handle both possible cases: * if / else block* condition:…

As an aside, there is clearly something not working in the community site with this thread as it keeps splitting answers in a single thread into different ones. Perhaps a community leader is moving it back and forth between "discussion" and "question" type. Regardless of that... I recommend pausing and merging those two…

Hi @Eran Roiter How do you want to compare the issues from the two filter results? What questions do you want to answer? For built-in dashboard gadgets... If you want to inspect the details of the issues, and their fields, try the Filter Results or Two-dimensional Filter Statistics gadgets. If you want to see trends over…

Hi @Tomislav Tobijas I agree with your initial note at the end of the question, and...not only is this not a "better" practice, it is likely to cause several unintended consequences and problems for an agile team, such as incentivizing less collaboration and breaking trust with stakeholders. Regardless of those problems...…

Thanks for that information, and... If you have multiple input fields, of type checkbox, your rule would not use an advanced branch as each field as only two possible values: true and false. What do you want to happen for the four possible cases? * both false * sfccdev is false and muledev is true * sfccdev is true and…

Hi @Tomáš Škarpa -- Welcome to the Atlassian Community! Adding to the suggestions provided by Marc and John... Let's clarify a bit: what is the type of your user input, "sfccdev: field which you are trying to advanced branch over? I do not believe there is a multiple-select option field for user inputs. Are you instead…

Hi @John Funk Thanks for the article, and as a clarification on automation rule usage / limits: Rules start executing when something happens, detected with a "trigger", may have decision points using "conditions", and do things with "actions". When a rule triggers, that does not necessarily count as "1 usage count".…

I suggest looking at Lean sources for those. In my experience, Lead Time is unambiguous and Cycle Time varies by context: Lead Time: duration time from request-made until value-delivered to customer; i.e., "concept to cash" Cycle Time: duration time between two steps in a process. For example, Build Cycle Time would be…

Hi @Petru Simion _Simitech Ltd__ Short answer: I recommend reviewing the documentation (and perhaps contacting the support team) for any of the marketplace apps you want to use to learn how they define the measures they provide. For the apps I have reviewed from the marketplace, including Atlassian's interpretation of a…

@Gustavo Polo -- Please try to stay with one thread when responding. That will help people reading the question know if there are multiple solution approaches to try. Thank for the answers and rule images. And please refer to my earlier answer where I noted the JSON must be dynamically generated. This would maintain the…

Hi @Gustavo Polo -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.) * an image of your complete automation rule * images of any relevant actions / conditions /…

@llewis -- In the blog you linked to, that is showing multiple uses of the gadget on the same dashboard, each one selecting a a different Scrum board and Sprint. It is not showing a single gadget somehow configured for different teams.

Well done!

Hi @Aquiles Lázaro Hernández -- Welcome to the Atlassian Community! The documentation for the bulk edit endpoint: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-bulk-operations/#api-rest-api-3-bulk-issues-fields-post Describes the Assignee and Reporter fields as examples which can be changed…

Hi @Sergey Shkut For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.) * an image of your complete automation rule * images of any relevant actions / conditions / branches * an image of the audit log…

Hi @Paolo Pastorino That is the date format which JPD uses, helping to handle a range of values. For other things like filters and dashboards, we are "stuck" with those text values of the dates. Some possible workarounds are: * if exporting the data, parse the field to convert to a date type * if displaying the data in a…

I do not see an open defect for this symptom in the public backlog, although I do see suggestions for better abilities to disable all Jira Cloud animations, such as this one: https://jira.atlassian.com/browse/JRACLOUD-75139 Unfortunately, there are more and more of these animations and pop-ups being added as UX experiments…

Hi @bilyana_karayaneva Please post an image of your complete rule, in one single image, and of the audit log details showing the rule execution. Those will provide context for the community to help. Until we see those... Please explain what is not working? What you may be seeing is the Parent field replacement of Epic Link…

Thanks for that information, @Sunil Mistry I tried this and saw a UX error but the validator still stopped the transition. The steps to reproduce this symptom were: * add a validator to the workflow to prevent transition if a select / option field was empty * saved the workflow changes and returned to a JPD list view *…

Regarding the images you show in #2, why do you you have two rules with the same trigger and conditions, but which transition to two different status values? Where are the issues located that you are changing? Are they in the project Task-Planer, which is where the rules are defined?

Hi @Giancarlo Fiorletta The article which @Trudy P Claspill provides also covers the potential risks of using an automation rule-based approach to solve this need: service limits, rule halting, etc. Ultimately, Jira does not have built-in features to handle such cascading date shifting at this time. I have seen posts where…