Bill Sheboy Expert

Hi @Inayatulla Shaik -- Welcome to the Atlassian Community! Please review the documentation for the new, issue search endpoint as the default is to only return the id values. Any other fields must be specified in the request.…

Hi @Anna Mjau -- Welcome to the Atlassian Community! You are observing a long-standing limitation for rules, preventing filtering of the list because the first variable is not visible: Once inside of a long-format iterator, only data from the iterator scope, and lower, is accessible. For your scenario, you seem to only…

Hi @Santhosh Raj First, there is no "this" smart value for an unnamed list element in smart values. Where did you find that defined? Instead, there is the explicit {{.}} one or the implied one for chained functions. And, your use of the chained text functions is incorrect, and you seem to be trying arbitrary syntaxes.…

Hi @Devon Manelski -- Welcome to the Atlassian Community! For the payload you show, there is an extra quotation mark in the JQL before the project name. Kind regards, Bill

Hi @Rosa M Fossi Which trigger is your rule using? If your rule is using the Work Item Created trigger, one possible cause is... There are known racetrack timing problems with that trigger where occasionally the rule can start before all the data is available; the work item may even be in an unstable state with no type…

Hi @Ellen Gruebbeling Thanks for explaining your scenario and what you have tried thus far. As a tip, for automation questions it helps to post an image of your actual rule and the audit log details to provide context. From what you show, you are trying to increment the work item key values and that will not work. The key…

Hi @Haddon Fisher FYI -- one way to try that second approach with less maintenance is to call the work item read endpoint, and then create that key / value pairs string using {{issue.fields}} as text for the source. Although it would get messy quickly for structured fields: users, ADF, etc. The risks I noted were for this…

Hi @Christian Piermayr That error seems puzzling to me: it normally indicates the field is selected from the dropdown list and provided with JSON in the edit action. Let's try this: disable your current rule, and re-create it from scratch. Then re-test it. That will determine if the stored rule was somehow corrupted due to…

Hi @Viktoriia Golovtseva _TitanApps_ As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording, and not just in your profile name / badge. For more information, please see: Atlassian Partners - Rules of Engagement…

Hi @SJ -- Welcome to the Atlassian Community! First thing: your question seems to indicate you are on a Free license level. If that is so, please note there is a limited number of rule usage executions per month, and so the rule shown likely will only succeed if you have very few work items. Back to your question... If you…

Hi @markus_neuwald_canon_at I added this separate thread so you can comment and accept this one. That will help others reading this in the future with similar questions. Thanks! Some additional things to check are the work item fields and permissions: Using this how-to article, you may confirm if that field is available to…

Hi markus.neuwald@canon.at Some additional things to check are the work item fields and permissions: Using this how-to article, you may confirm if that field is available to the work item and its value. The essential steps are: * identify the key for the work item you are trying to update * with a new browser tab, enter…

Hi @Kelsi Flores Just following up to check if this answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks!

Hi @Robby Keefer For the case you describe, work item linking happens as a separate step after a create. You may observe this by viewing the history for a work item as it shows both steps...even though they occur very close together in time. The same thing happens when viewing an Idea and creating a "delivery ticket": it…

If I understand your question...Let's say we are using conditions to decide if we should assign a work item to "Bill". I could add an additional condition so it does not assign when it is already assigned to that person: * ... * if / else block* some conditions to decide to assign to "Bill" * user condition: assignee is…

That is a good start, and... I recommend not adding conditions directly to the trigger, and instead add the conditions after the Re-fetch Work Item Data action. (The new feature to add conditions directly to triggers can have timing problems, causing side-effects.) For the "Add value to the audit log", this is to confirm…

It would be a new rule to test it...and what you describe seems to confirm why using a test rule would help. By creating it, you will learn what is possible and how to adjust the conditions for your needs. I would start with the simple test rule, and ignore the part about the lookup table for now.

Hi @pszwajkowski -- Welcome to the Atlassian Community! Short answer: I do not believe that is possible at this time. There are several open suggestions to improve audit logging related to site webhooks, including this one which is more than a decade old: https://jira.atlassian.com/browse/JRACLOUD-41463 I also checked the…

Hi @John Smith As I do not know all of your cases, or how you want to handle each one, me creating a rule may not help as much. I recommend building a test rule with a Work Item Created trigger, and adding the User Condition to test the scenarios, perhaps writing to the log to confirm the results. For example, if you…

Hi @armel.kaptue -- Welcome to the Atlassian Community! Here are the various work item search endpoints, including both the active and deprecated ones: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-group-issue-search Kind regards, Bill

Thanks for the additional information, @Sven Meier As you cannot post images, you could also list your rule steps in bulleted text, adding any smart values used, and copy-and-paste the audit log results. That context will provide some context for what you are trying. Back to your question... You are correct the min…

Ah, your rule is using the generic Work Item Updated trigger... Let's start with the {{initiator}} smart value is the user who performed the action which triggered a rule. And, work item assignment is a different event than updating, and so that would use a different rule trigger than an update. So for the update, you…

Hi @John Smith -- Welcome to the Atlassian Community! Without seeing your rule and all the assignment criteria involved... One way to solve this would be to capture who assigned the work item in a custom field (with an automation rule). Then your rule triggered on other field updates could check if the "assigner" was not…

Hi @Martin Grühn -- Welcome to the Atlassian Community! Unrelated to your avatar visibility question, but related to the retro process you describe... There is some risk allowing people an essentially unlimited amount of time to add cards / ideas before the session. It could create a challenge where there is not enough…

@Joseph Wilkinson -- Short answer: not with built-in features. That would require checking each board / filter in the site to check if a work item is returned by it. Theoretically...one could write an app which gathers all boards using a REST API endpoint, and then use another endpoint to gather the work items on the board…

Hi @Iryna Menzheha_SaaSJet Short answer: for non-trivial team processes, there are limited features in Jira to manage and report flow and work in progress (WIP), and thus using marketplace apps may help fill those gaps...but first, pause to discuss and align with the team on why, what, and how to effectively manage flow…

Hi @Zak Siddique Yes, and...to the suggestions offered: The new feature to add conditions directly to triggers has racetrack timing problems (among other challenges), and so I recommend not using this feature until Atlassian improves the architecture for event-raising and rule trigger ordering. Instead, use your rule…

Hi @Varvara K_ That seems to be a marketplace app rather than a built-in, Jira feature. I recommend checking the vendor's documentation or contacting their support team: https://marketplace.atlassian.com/apps/1229958/issue-sync-pro?hosting=cloud&tab=overview Kind regards, Bill

Hi @Venkatesh G For a question like this, context is important for the community to help. Please post the following: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches…

Filtering for a specific count of items cannot be done in one step because: * JQL is not a SQL and does not have support for operators such as TOP 20, and * the {{index}} smart value for lists cannot be filtered upon directly. A simple workaround to get fewer, but perhaps not exactly 20 items, is to add more criteria to…