Bill Sheboy Expert

Please post the audit log details showing the rule execution after your changes. This will confirm which work items the rule attempted to process. And just to confirm, are all of the work items involve in a single space / project: the parent and the children?

Hi @Gelo Gonzales From what you describe, I assume you have: * one or more company-managed spaces (i.e., Jira projects) * have created a saved filter spanning those spaces, perhaps with additional criteria by Status values, with an ORDER BY Rank ASC expression at the end * have created a Kanban board for that saved filter,…

Hi @Christopher Holmes Repeating my earlier question when you posted this content as a question: ...where did you create the rule in the image you show? Is this an actual rule in Jira? The image appears to show a trigger with Field Value Changed for a work item field, with the Team and Created fields selected. But,…

Hi @ckopanon Please review the earlier posts in this thread where I describe your Lookup Work Item action's JQL does not reference the parent...and thus you may be looking at the wrong work items. Within the branch, if you wanted the lookup to use the parent, the rule would look like this: * trigger: field value changed,…

Thanks for that information, @Elisa Chimal as it appears this was user permissions related, as suggested by the answer from @Varsha Joshi 

Hi @Cal Nelson -- Welcome to the Atlassian Community! Thanks for posting that image! I wondered what this new-this-week, surprise feature looked like when it was only announced in the weekly blog: https://confluence.atlassian.com/cloud/blog/2026/02/atlassian-cloud-changes-feb-2-to-feb-9-2026 Kind regards, Bill

How many users are set up in your free Jira site? Are you using Sprints, and thus a Scrum board versus a Kanban board?

Hi @RL I recall the "days in column" feature sums the total time a work item is in a column based upon the changelog history. Thus, it adds up the time and divides by a 24 hour day. This time could include a work item being in a column, leaving it, and returning again later. Kind regards, Bill

Hi @Elisa Chimal Have you asked your teammate who cannot see the work items to try browser-related diagnostic steps? For example: * log out of Jira * clear the browser cache from settings * close all open browsers * open one browser, and try logging in again to see the work items Kind regards, Bill

Hi @Varsha Joshi Team-managed spaces do not support configuration of the filter, including changing the shares. Below are the open suggestions to add that feature, although the current recommendation from Atlassian is to use a company-managed space when one wants to configure a filter: *…

Hi @Jeremy Drexler There is no publicly visible project in JAC for any JPD suggestions or defects which we can watch / vote for. The only thing like it the Atlassian team has shared with the community is their roadmap of large-scale ideas:…

Still I wonder, where did you create that rule? As I noted, the trigger the image shows cannot use the Created field for an Atlassian Automation rule. Thanks.

Hi @Christopher Holmes First, are you asking a question or instead creating an article to explain something? You posted this as a question. Next, where did you create the rule in the image you show? Is this an actual rule in Jira? The image appears to show a trigger with Field Value Changed for a work item field, with the…

Yup, something appears to have changed...As you are on a paid license level, I recommend working with your Jira Product Admin to submit a ticket to Atlassian Support here: https://support.atlassian.com/contact/#/ When you hear back from them, please post what you learn to benefit the community. Thanks!

Hi @James Deam That seems to be a defect in the code macro. While I could not find that specific symptom in the public backlog JAC, I did find a related one which mentions code formatting problems and the absence of a plain text editor / macro option: https://jira.atlassian.com/browse/JRACLOUD-72631 Kind regards, Bill

Hi @Vikrant Yadav Without seeing your entire rule and the audit log details, I wonder what error is showing. A work item can be assigned using the email address with the Edit Work Item action, but not the Assign Work Item action. The "trick" may be one of timing, where the email address can be first extracted to a Create…

Hi @Adrian Avalos Your rule will need to use global or multiple-project scope to access the issue in the other project. When you cannot change the scope for some reason, the only other approach is more complicated and requires directly calling the REST API endpoints using Send Web Request to modify the issue...regardless…

Hi @Mateusz Janus For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant trigger / actions / conditions / branches * an image of the audit log details showing the rule…

Hi @Jason Pace and @John Funk I wonder if what you observe is related to this one: https://jira.atlassian.com/browse/JRACLOUD-96737 Please read through the comments to note people's observations about changes to pinning behavior for the Development panel / field. Kind regards, Bill

Hi @Trudy P Claspill I recall discovering that symptom by experimentation with Start Date and Target End...although I just tested again and {{issue.Start date}} worked as a date without conversion. Thus, something has changed over time, and the text format is not the cause of the symptom seen by @ckopanon Either a…

Hi @ckopanon Start Date is one of the date fields which appears as text to automation rules...similar to other roadmap fields. The workaround for your scenario is to convert the value with the toDate function before attempting to use the min function, and then convert back to the necessary date format as text. For example:…

Hi @이윤신 That is a known symptom, and here is the defect in case you want to watch it for progress: https://jira.atlassian.com/browse/JRACLOUD-79567 Kind regards, Bill

Hi @Diego Arturo Bustos Aponte As this is a very old, resolved thread, I recommend creating a new question with the "Ask a question" button at the top of the page, and perhaps add a link to this thread for context. When creating your question, please remember to post images of your complete rule, the audit log details, and…

Here the link to the suggestion to support project keys and ID values, including a link back to the 2018 community post when Code Barrel's team acknowledge the limitation: https://jira.atlassian.com/browse/AUTO-839…

Hi @Kyrah Johnson Adding to the suggestions from @Trudy P Claspill ... If you still want to use the lookup table as the source of matches, you could try: * create the table * remove the branching * use the table's entries function to extract just the values to build a dynamic regular expression using list iteration * use…

Hi @Aanchal Bhatnagar I recommend checking the marketplace to search for apps / dashboard gadgets to meet your needs: https://marketplace.atlassian.com/ And first...perhaps pause to list what you want to measure / see in such visualizations. What are your specific constraints? Perhaps also discuss this with your Jira…

Yup: gotta use the project ID rather than the key when one wants to dynamically select the project in a rule action such as clone, create, etc. I wish there was a clone work item endpoint to simplify such scenarios. Better still, a clone-work-item-tree-with-children-whilst-preserving-the-order-of-children endpoint :^)

Yes, I agree with your concerns: better JQL support and UX display are needed for this field type outside of JPD features. Improving this handling is noted as "up next" on the JPD roadmap for item JPR-29:…

Hi @Brian Pearcy What problem are you trying to solve? That is, "why do this?" Knowing that may help the community suggest alternatives. Until we know that... Jira Product Discovery (JPD) uses its own date format, different from the date or date-time picker for other spaces. The JPD format allows selecting a single date, a…

Hi @Dinonath Khan As this is a public forum, I recommend removing / obscuring your actual email addresses from all of the posts in this thread in the text and images. That will likely reduce the risks of unsolicited emails. Thanks! Kind regards, Bill