Bill Sheboy Expert

Thanks for the additional information, @Kieran McShane Is the sprint you want the most recent one by date? If so, you may use the max list function to get the dates, regardless of the sprint's state: * {{issue.sprint.startDate.max}} * {{issue.sprint.endDate.max}}

Hi @Kieran McShane -- Welcome to the Atlassian Community! There are several ways to do this, depending upon when you want to do it: * When the sprint starts* Use a rule triggered on Sprint Started, and that will provide the single smart value {{sprint}} with its date attributes * Grab those dates to save them in created…

Perhaps work with your Site Admin to submit a ticket to Atlassian support if you are seeing inconsistent results with the revised Confluence user search endpoint. If you are on a paid license, you may do that here: https://support.atlassian.com/contact/#/

Gotcha, and remember to check the rule scope (in the details at the top) to ensure it can "see" all the relevant projects.

Thanks for that update, @Troy Anderson To summarize: using the REST API directly works but the new Edit Confluence page with the same content does not. I recall other questions for this new action where some markup caused problems...possibly due to how the action processes the content before making the very same endpoint…

Hi @Christian Piermayr Did you try my suggestion from the other post to add all of the Contributors at one time? https://community.atlassian.com/forums/Automation-questions/Re-Re-Finding-Mentioning-a-User-in-Comment-and-Cust/qaq-p/3107805/comment-id/15214#M15214 Kind regards, Bill

Hi @Brandon Viertel First thing, I am not using Journeys with JSM, and my suggestions are based on what I know about automation generally and the documentation on Journeys. With that out of the way... My understanding is Journeys create a specific work item, and automation rules to interact with them are global scope for…

Have you tried other endpoint calls with the same credentials using Postman to confirm you are getting any results? This would rule out a permissions problem. Thanks!

Thanks for that information, @Joseph Wilkinson For overall, "monitoring views" of multiple Scrum team boards, I have also seen a single Kanban board which shows the rollup. Back to your question: yes, I believe for multiple Jira Scrum boards as you describe, the column mappings of ["not started", "in progress",…

Hi @Christian Piermayr As this is an older thread, I recommend creating a new question with "Ask a question" and including a link back to this one. That will ensure the maximum number of people see it to offer suggestions. Otherwise, only people following the older thread will see it. Until we see your new question... It…

@Marc -Devoteam- -- You are correct about the users' access, and my assumption was the Confluence user set is likely a subset of the Jira ones. If not, other methods are needed. @Jamie Wolman -- How are you using that endpoint call and with which user's permissions? For example, if you log into Jira with a browser, open an…

Hi @daniel.jones -- Smart values (including created variables) scope depend upon where they exist and where they were created in the rule. Please see this article I wrote on the topic to learn more. For your scenario, as long as any values are created outside of branches, you should be okay. More specifically, for the…

Hi @Marvin Brand For that first method, you may store the entire {{lookupIssues}} result in the table, and then use it directly. This is a good technique to have multiple lookup results as it preserves the object structure. For example: * action: lookup work items, with your first JQL * action: create lookup table*…

Hi @Jamie Wolman You show a CQL search, and that would find Confluence content, not users. Instead, please try using the Jira find user endpoint to search by email address: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-user-search/#api-rest-api-3-user-search-get Kind regards, Bill

Hi @Joseph Wilkinson First a question: would you please describe your team(s) process such that the single work item is on two different Scrum boards? I have observed this for Kanban boards with interconnected team flows yet not for Scrum. The status category has no impact on completion: Jira Scrum boards determine…

Hi @Marvin Brand I just saw your new question, and gave an answer to your other post: Long-format iterators have a known limitation where they cannot "see" data from outside their scope. And so once inside those {{#lookupIssues}} ... {{/}} iterators, they cannot access other issues, variables, etc. There are two possible…

Hi @Marvin Brand As this is an older thread, I recommend creating a new question and including a link to this thread for context. That will ensure better visibility and focus on your scenario. Otherwise, only people following the older posts will see it. Until we see your new question... Long-format iterators have a known…

Thanks for that information, @Prathap DL and what you show is puzzling to me. My understanding is when a link type is directional, rules with a Work Item Linked trigger always run in one single direction, regardless of on which work item the link was added. Your rule appears to show something differently...or the link type…

Thanks for that information, @daniel.jones as it narrows down the scope a bit. And, based on the question tags I am assuming you are using Jira Data Center. If not, please let me know. For a single story rule, which adds a lot of subtasks, the issue creation will take a bit of time...and adding the links afterwards will…

Hi @Prathap DL What have you tried thus far to solve this? If you have a rule that is not working as expected, please note context is important for the community to help. To provide context, please post: * what types of projects are you using: company managed, team managed, JPD, etc. * an image of your complete rule, in a…

Hi @Radia Dev Yes, and...to the suggestions from @Jack Brickey Even during normal processing conditions, automation rules do not always trigger exactly when the event happens that triggered them. Indeed, this causes a variety of racetrack timing problems in rules. And so comparing to "now" may not be accurate for your…

Hi @daniel.jones Without seeing the specifics of the rule which creates the subtasks... You might be able to use the Lookup Work Items action or the Story's smart value {{issue.subtasks}} to do this, and it depends upon two things: * How long is the current rule?* You describe creating 40 subtasks. Unless those are all…

Hi @Agnes Bodor -- Welcome to the Atlassian Community! Once inside a set of double-curly brackets, additional ones are not needed. And, the lookup table's get function does not need quotation marks when using a smart value as a parameter. Please try this expression: {{tableVar.get(varIter)}} Kind regards, Bill

Hi @Wendy Quon Your rule is building a JSON expression dynamically, using smart values. Please try first creating a variable to store that JSON, and writing it to the audit log: * action: create variable* name: varJson * smart value: your JSON expression * action: log* {{varJson}} * action: send web request* use…

Hi @Agnes Bodor -- Welcome to the Atlassian Community! You are encountering a limitation of the long-format of list iterators: Once inside the iterator, no outside data is visible. Only data from the iterator, and lower can be accessed. Thus, your MyComponent variable cannot be used to filter the list. The workaround for…

Thanks for that information, @David Nadri and, there are a couple of ways so solve this with automation: archiving and a custom field filter. With archiving, and automation rule could check daily, and archive the work items which are released and older than 6 months. Then they would automagically not display...but still be…

Hi @Emanuelwilliam -- Welcome to the Atlassian Community! Assuming you are using Jira Cloud... Context is quite important for automation rule questions, and you did not show a specific rule or evidence for your belief it has performance delays. If you post your rule and the audit log details, the community will be better…

That will not work as you described... Imagine creating swim lanes based on a different JQL query, such as based on the Created field and the current date / time. Dragging a work item would not change when the item was created...or change the current date / time. And as the JQL for swim lanes could check multiple field…

Yes, that should work for the scenario you described. Have you tested with it yet?

Hi @Gaurav Pawaskar -- Welcome to the Atlassian Community! Would you please post images of your complete rule, the conditions, and the audit log details showing the rule execution? Seeing the actual content may help explain what you are observing. Until we see those... Labels cannot contain duplicates, although they can…