Bill Sheboy Expert

That would seem to indicate you are looking at a different field; however, which values are you looking for in that result: the id or the value? When you edit a option / cascading field, you may set the selections by the id or the value. The id is the internal Jira value for the field and is not user-controlled. In some of…

The problem is related to the order of your rule steps and the issue's state... When a rule edits an issue, it uses the state / field values at the time the rule loads. And so each of your edits is restarting from that point. The same is true for issue transitions. First, I recommend combining all of those field edits in…

Hi @Robert Nichols Short answer: please post images of your complete rule and audit log details showing the rule execution. Those will help clarify what is happening. More information... That symptom is quite odd, and possibly from some another cause, based on the rule you describe. Instead maybe the audit log display…

Hi @Christy Kennedy As that is a marketplace addon for checklists, I recommend checking their documentation / contacting their support team to learn how to do this. I know some other checklist addons use a custom field to hold the data, and that can be monitored for changes with either the Issue Field Updated or generic…

Thanks, @Filipi Lima !

Ah, thank you for clarifying! Please try disabling / removing one, and change your rule to use an if / else condition to handle the different cases in one rule: https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/#If-else-block

You seem to already have that addon dashboard gadget, so it may be just a matter of understanding how it works. Regarding built-in features, that depends upon what you mean by "Done %", and for which issues. For example, for an epic view you may see a simple progress bar by count of the child issues with the percentage…

If you use that how-to method, for an example issue with the parent / child values set for a cascade field, both should be visible in the JSON.

Hi @Karyna Grygorova That is not possible with the out-of-the-box features of JQL. Although it may be possible to adjust the JQL to exclude weekends, there is no way to manage any included holidays within the range. There may be marketplace addons which add features to JQL that handle your scenario. Kind regards, Bill

Hi @Giovanni Sanchez For a scenario like this where an issue is created in another project, a better way to prevent duplications is to explicitly check if that issue exists before the create issue action. That could be done with a JQL condition or the lookup issues action plus a condition. As the issues are in different…

Hi @Robert Campbell -- Welcome to the Atlassian Community! That gadget appears to be from a marketplace addon, and not a built-in feature of Jira Cloud. I recommend contacting the vendor's support, from their marketplace page, to check their documentation or email the support team: https://marketplace.atlassian.com/search…

Hi @Analia Busso I do not believe that is possible with the built-in features of Jira Cloud. You could try calling the REST API functions, getting up to 100 board records at a time, and that would show the type as "scrum" or "kanban" for the company-managed…

Hi @Shaun Speers Did you add that custom field to the site or is it from a marketplace addon / app? Regarding the values you are trying to use in the JSON, have you confirmed they match exactly, including any spaces, to the allowed values? One way to check that would be to create an issue with those exact values for the…

Hi @Michael P_ O_Hara That appears to be the Summary page for a Jira Work Management project, and so the done items drop off of the view after 14 days. Is that the case for the items not displaying on your view? Here is a suggestions to make that timeframe configurable, like it is for some other project types (e.g., Jira…

Hi @koutarou ishibashi I suspect the answer is, "no". There are many ways throttling can occur, some of which are caused by errors on the Atlassian side and so out of customer control. I recommend (based on your earlier question about detecting throttling has happened) that once you detect throttling, actively check the…

Hi @Andre Silva 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 @Ariel -- Welcome to the Atlassian Community! I do not believe the behavior you describe is from built-in features. Do you have a marketplace addon or automation rule running which are automatically logging work time? Please check with your Jira admin to confirm those things. Kind regards, Bill

Hi @Jacob Wisner Thanks for this information! Three questions... How does one group / ungroup shapes? I did not see that in the shortcuts. What other templates are you considering adding? For example, such as mind maps, whiteboards including Confluence macros for Jira data, etc. I notice when shapes are grouped, then…

Hi @Alexis Manouvrier -- Welcome to the Atlassian Community! Yes, and...to Trudy's answer: The correct field is now the "Issue color", and the custom field id may be used in that JSON edit to change it. And...a later Jira change altered the allowed color values. When I just checked some examples, the color values appear to…

Your lookup issues action has the curly brackets in the wrong place in the JQL. Please try this: issue IN linkedIssues({{triggerIssue.parent.key}}, "relates to")

Thanks for that information. And if you need this one time only, calling the REST API function would help, as Jerrold suggested, or... Find a marketplace addon which can do this type of field value import, install a trial, add the field to try it out.

Hi @Jeevan Kumar K G What have you done thus far to try to solve these needs? If you have started automation rules and they are not working as expected, please post images of your rule, the audit log details, and explain what does not work as you expected. That will provide context for the community to offer suggestions.…

Hi @Hana Kučerová For better or worse, I hypothesize many customers have a TMP project even when they do not want it, as JPD seems wholly built upon it. Anyways... I have supported teams who are self-starters (or think they are :^) regarding agility, and they insist on having the flexibility of a TMP project to make…

Hi @Monique vdB After reading a community question about articles being re-located to App Central, I went back and re-read this guidance at the start this thread: I have noticed articles in other areas, such as in agile and teamwork, which do not directly mention an app from the marketplace vendor / employee writing the…

Hi, Mikko -- Welcome to the Atlassian Community! For the rule you describe, there are a couple of potential challenges... First thing, there are known problems with the change log and fix version field, such that it may not accurately reflect what has changed: https://jira.atlassian.com/browse/JRACLOUD-80486 There is no…

Hi @Jar Lady Yes, that should work. What do you observe happening? And, have you confirmed that the content of the {{webhookData.body}} (or {{webhookReponse.body}} ) contains the information in the format you expect? You could confirm this by writing the value to the audit log and checking after the rule execution. For…

Hi @motherg First thing, well done in your clear explanation of the scenario! I believe that would be possible using an automation rule, triggered on the issue linking, and using conditions and branching to update the correct epics. This rule would need to be multiple-project or global in scope as it is modifying multiple…

Hi @Hashem Sarsour -- Welcome to the Atlassian Community! What problem are you trying to solve? That is, why do this? Knowing that may help the community to offer better suggestions to solve that problem. Thanks! Kind regards, Bill

Hi @koutarou ishibashi You can try adding a global scope rule, with the Service Limit Breached trigger to notify at various thresholds. We used that at my last position to notify the site admins of problems like run-away rules, etc. As throttling is often caused by a bad rule design, broken assumption, or mis-use case for…

Hi @Rakesh Parte -- Welcome to the Atlassian Community! For a question like this, you may also want to search in the Developer Community: https://community.developer.atlassian.com/ Here is the information on the webhook retry policy: https://developer.atlassian.com/cloud/jira/platform/webhooks/#retry-policy And here is the…