Bill Sheboy Expert

Hi @Brian Liddle I do not believe that is possible yet. In this community post on that topic, there are links to suggestions to add the feature and some work-arounds. https://community.atlassian.com/t5/Jira-Software-questions/Is-there-a-way-to-use-the-JIRA-API-to-retrieve-Release-Notes-of/qaq-p/1678046 Kind regards, Bill

Hi @Vineet.Kotian Yes, and...to the other answers provided. Synchronization rules can be challenging when you want to cover *all* possible scenarios. Please consider which ones you want versus need, as that will determine how many rules you need and what they do. For example: * sub-task added to a parent issue * sub-task…

Hi @Benjamin Høegh As others have noted, this symptom is possibly caused by a race-track condition spanning your rules. Often the solution for this is to change your approach. For example, collapsing multiple rules into one, changing rule triggers, etc. To help with that, the community will need to see images of your…

Hi @Domi Yes, that is possible. The field used for this is the epic's "Issue Color", and that can be edited using an advanced edit with JSON, as described here: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Text-custom-field For example, { "fields": { "customfield_10017": "orange" }…

Thanks, Darryl. I am going to start book marking these as stuff like this repeatedly comes up. And remember the possible "gotcha" noted in the earlier thread when the attribute names need to change between the field definition and attributes. (e.g., id versus value)

Hi @Darren Nicas -- Welcome to the Atlassian Community! Yes, this scenario is solvable...but not with advanced branching. First some information about branches in rules: * Branches on one-and-only-thing (e.g., Current Issue, Epic Parent, etc.) are run in-line, as if the branch did not exist. And so the rule flows as you…

I believe your earlier expression was closer before...perhaps try this: {{#Issues}} {{#if(and(equals(status.name, "Closed"), gte(updated.jiraDateTime,now.minusDays(10).jiraDateTime)))}} <a href="{{issue.url}}">{{Summary}} - </a>{{Comment.last.body}} {{/}}{{/}}

Hi @Amit Shaw Please try using the toBusinessDay function for that: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ Kind regards, Bill

Hi, @Simmo I do not personally have a use case for dynamic loading of tables yet...although I have seen community posts where people had data in other systems which they wanted to lookup in Jira. Even with those, they are limited by the smart value, function parameters behavior I noted. A few possible use cases would be…

Let's put these two tests together to learn if we are missing something obvious: After your trigger, and before the branch, add a write to the audit log with the JQL you are about to use in the branch. That will confirm, in context, what the branch is about to use. Then run your rule and post an image of the audit log…

Hi @Francisco Hazera -- Welcome to the Atlassian Community! In your "closed" section, you do not have a condition which produces a true/false. What test are you trying to perform for comparing updated and now.plusDays(-10)? Did you want to use greater than or equal to, gte()? Please try adding that to observe the results.…

Argh...this is one of those cases where a smart value function cannot take a variable (or smart value) as a parameter. I'll ponder a bit for other work-arounds, and until then you may want to work with your site admin to ping the support team about this one: https://support.atlassian.com/contact/#/

Yes, and... What do people think of dynamic creation of a Lookup Table, such a from a webrequest response? (e.g., providing a list of key/value pairs to a creator) This could mitigate the problem where often smart values (particularly created variables) cannot be used in functions, allowing the table to be used as a source…

For your scenario, I believe you want that checkbox unchecked...so all issues are found. Did you see my earlier comment about rules getting "glitched" by too many edits/publishes? Have you tried to disable this rule, recreate it from scratch, and see how that helps?

@Isaiah John -- Automation rules have an action to write to the audit log: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Log-action Please add that action to your rule and paste in the smart value expression I provided. After your rule runs, you may then review the results in the audit log…

Hi @Brandon Barski -- Welcome to the Atlassian Community! That is a good work-around. Another we have used is to unassign an issue when it is ready to be pulled to the next step. Then people can filter on unassigned issues (or glance at the board) to see what to pull next. Kind regards, Bill

Lauren, are you using Jira Cloud or Jira Server / Data Center? For Cloud, the database is not directly accessible. I have not done what you asked before for Server / Data Center versions. And to do what you ask with out of the box features you can... * Use the built-in control chart report to see the time in status. That…

Hi @Isaiah John My guess would be "probably yes" as that data is available for issues normally via the subtasks attribute, such as {{issue.subtasks}} I recommend testing this by writing to the audit log, perhaps like this example: {{lookupIssues.first.subtasks.first.assignee.displayName}} This would log the display name of…

What is not working as you expect? Would you please post an image of the audit log showing the details of the rule execution? You appear to be using MS Windows, and so can use the built-in snipping tool to capture the screen image area. Without seeing those, I suspect a problem is the rule conditions are testing the…

Hi @Lauren Hinrichs Each change to an issue, like a status transition, is recorded in the issue history. However that data can be difficult to access. There are JQL operators to help with that, but perhaps not how you are asking. Automation rules can also detect a status change, and perform actions as needed. What problem…

Hi @Kevin Kashou -- Welcome to the Atlassian Community! After you clone the issue, you need to first Branch to Most Recently Created Issue. Then you can transition that. And also...Because this will try to edit the issue in the other project, this rule will need to be global scope, and then select both projects. You appear…

If a rule triggers, that counts as an execution. That applies even if the rule does nothing other than be triggered.

Hi, @Saira Please create a new question when you have a new question...rather than adding more questions to an existing thread. In the meantime, please read about smart value, list filtering here to do what you asked: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 Kind…

Hi @saje -- Welcome to the Atlassian Community! Adding to Trudy's thoughts... I also wondered about this scenario as Jira Product Discovery (JPD) moved from beta to general availability because my understanding is a Jira user *must* have Creator or Project Admin permissions to make such changes, and that will be charged…

That does not appear to be possible. JPD custom fields like that are dynamically calculated, apparently when they are drawn in a view. And so they have no value available for JQL because the value is never saved. There is a separate community group for JPD, and so you may also want to check there in case someone has found…

Thanks, and now let's go further to confirm your custom field contains what you expect by writing these to the audit log. Remember to update that with your specific custom field's id value. The field is: {{webhookResponse.body.issues.first.customfield_12345}} The field as a number is:…

My disclaimer is that I am just a Jira user, and do not work for Atlassian or any marketplace vendor... I have used Great Gadgets from Stonikbyte and found them helpful. Before selecting an addon, I suggest listing out what you want to measure / visualize, and then compare the products to learn what may help.

I wonder...unfortunately some smart value functions will not accept a created variable as a parameter. Let's try this... * write that value to the audit log to confirm it is valid: {{applicationIndexFinal.asNumber}} * enter a hard-coded value in that get() to confirm it works as you expect

In that branch, do you have this option checked: "Only include issues that have changed since the last time this rule executed" If so, please uncheck it and the issues will be returned to process.

Would you also post the audit log from before you removed the branch and the rule did not find anything? That will show us the complete flow. Thanks! By the way...another thing to try: rules can sometimes get "glitched" by too many edit/save/publish cycles and so they stop working. There is something in the rule editor…