Bill Sheboy Expert

Yes, and... You may find your issues having attachments using a query: project = myProject AND attachments IS NOT EMPTY And then iterate over them to get the attachment information using the REST API that Nic suggests: https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/attachment-expandForHumans

Hi @JAKE I recommend not deleting issues, and instead add a custom field to mark them as Abandoned. Deleted is gone forever in Cloud version; no undo is available and backup/restore is cumbersome. Using something like Abandon allows teams to remove those issues from boards and reports using filters *and* the Abandoned…

Could this be related to this issue, which appears to impact more than just the French language based upon the comments: https://jira.atlassian.com/browse/JRACLOUD-62929

Hi, community! How about Age of WIP (work item age)? (1) Add a custom numeric field, AgeOfWip (2) Create the rule with a daily schedule, looking only at "in progress" and non-cancelled items (3) Edit the custom field to calculate in calendar days…

Thanks for the additional information @Ashish It appears that the edit is trying to change the linked issues from the branch, rather than the original triggering issue, and so that may be doing something different than you needed. Before I suggest an alternative... Please describe the problem you are solving by putting the…

Please note: Sometimes the double-quotes are needed and sometimes not... Smart value expression parsing appears to use the period (.) to de-reference elements, and so when the entity property contains a period it needs to be enclosed in double-quotes. That probably triggers some escaping logic. I haven't clearly identified…

Chris, would you please mark this one as solved/answered? That will help others in the community find solutions faster. Thanks!

Please try to uncheck the checkbox: "Only include issues that have changed..."

If there is no JQL associated with that scheduled trigger, that would explain the problem...although it creates another symptom: I thought the rule raises an error if there are no issues when you try to access issue smart values. Curious... Update: I just tried a scheduled rule without JQL, accessed an issue field, and it…

Hi @Aayush Mohanka For other automation in Jira Cloud, you may check the {{initiator}} and its fields to determine if the triggering entity was a user, automation user, etc. I do not believe this works for all of the DevOps triggers. Is that field/smart value available in your problem context? Best regards, Bill

Hi @Chris Sandford Would you please post an image of your entire rule? That will provide some context that might reveal what is happening. Thanks! Best regards, Bill

Hi @Nikita Krivda There is no built-in way to find these added issues using JQL, and there is a suggestion to add this capability: https://jira.atlassian.com/browse/JSWSERVER-20097 If you have the ScriptRunner add-on, there is a function you may used to find them:…

I tried the rule I suggested and it worked for me. Would you please post the error you are seeing, from creating the rule or in the audit log when running the rule?

Yes, that is a known problem (design choice) that operators and functions do not work inside of the iterators. I submitted a defect on Cloud version and support said, "by design". The only work-arounds I have seen were to use a created variable (for single values) or to pre-compute the value in a custom field (for multiple…

Hi @Peter Strassmann -- Welcome to the Atlassian Community! Did you note the troubleshooting steps at the bottom of that linked article? Please take a look at those to see if any of the cases apply to your instance. Best regards, Bill

Thanks, @Richard Vencu Perhaps if you post an image of your current rule that will help people give you ideas. For example, techniques to work-around some of the context/scope issues for information access within a rule with techniques like created variables, custom fields, or entity properties.

Hi @Manrique Soto For something like this, please consider creating a new question or staying on the original thread. The answer to your question is: yes. The earlier examples all use date/time fields. Here is an example I use to measure Lead Time in fractional days.…

Hi @harsh.bhardwaj Thanks for explaining what you are trying to accomplish. The built-in email handler will not support that so a plug-in sounds like a good route to try. The only other option I can think of is to build your own application/email parser and use the REST API to add the issues. I do not have a recommended…

@Ashish Please run the rule you created, post an image of the audit log details for that run, and describe what is not performing as expected. Those details will help people provide more focused suggestions. Thank you.

HI @a2mun -- Welcome to the Atlassian Community! Have you answered your questions? If not... You have already considered ideas about different ways Jira could help. I believe there is no "best" way to solve what you ask; what your team does at a point of time is what works for you. And Jira is a tool to help you manage…

Hi @Richard Vencu Did you see this post, which shows at the end an example to get the latest comment using the REST API? https://community.atlassian.com/t5/Jira-questions/How-do-I-get-the-latest-comment-via-REST-API-call/qaq-p/1113527 Best regards, Bill

Hi @Moheeb Qupty -- Welcome to the Atlassian Community! I believe that is not possible with automation for Jira. There are some suggested improvements in the automation backlog around this idea, and the notes indicate there are other marketplace add-ons specifically supporting cross-instance communication which are better…

Hi @JRodney Estrada You may easily move the issues from one project to another, other than the obvious mapping issues for workflow, status, component, etc. History is another story, as many of the entities driving history belong to the project: sprint and version. You could choose to just move the open issues from Project…

Hi @[deleted] I do not believe this is possible with out of the box Jira. You would need to iteratively compare the Start Date and Due Date for multiple issues, which is not something basic JQL can do. You may be able to do this with one of the marketplace scripting add-ons. But if you are going to get an add-on, you may…

Thanks for that information. This seems like an issue with the Resolution not being set for your "completed" status values in workflow. You have "Done" and "Complete" and "Cancelled" as status values in the completed column. Are they all end-points or does one lead to another? Depending upon your flow, the solutions could…

Hi @[deleted] -- Welcome to the Atlassian Community! I do not see a way to do that in their documentation. As a customer using their product, you may want to contact their support directly to ask if this is possible: https://marketplace.atlassian.com/apps/1215695/easy-agile-roadmaps-for-jira?hosting=cloud&tab=support After…

Hi @Trena Norcia To help provide you ideas, would you also please post images from your Board Settings: * your General settings (including your filter and any sub-filter), and * your Column layout with mapped status values? Thanks, and best regards, Bill

Hi @Mel Jensen To do this you may used Filters > Advanced Issue Search With a JQL query something like this: project = myProject AND labels IN (techdebt) ORDER BY Key Then, add the columns you want, such as Status. You can learn more about filters here:…

Agreeing with @John Funk on the limitations/work-around... There are suggestions in the automation rules backlog to support creating a rule to "move to top" as needed, such as on a status change: https://codebarrel.atlassian.net/browse/AUT-919 https://codebarrel.atlassian.net/browse/AUT-1074 Best regards, Bill

Hi @Ashish Is your link type "Implemented By" a custom link type you added or perhaps a renamed one? I do not see that one in my default values. If so, you may need to branch on all link types, and then add an advanced compare condition to check the smart value if the link type manually rather from the list. It is odd that…