Bill Sheboy Expert

Hi @Binod Bihari Das -- Welcome to the Atlassian Community! Please create a new question, including details of your workflow and a description of what you observe that is unexpected. Otherwise only the people following this old thread will see what you posted. Kind regards, Bill

I am unclear what you mean as your original question references Lookup Issues and now you are referencing Lookup Table, which are two different things in rules. Would you please post images of your complete automation rule, showing the details of each action, and of the audit log details showing the rule execution? Those…

I believe the feature you asked about is available for the Cloud version and not Server/Data Center.

Yes, I forgot to mention that as it was referenced in those suggestions for when the configuration option was set that way. I am glad to learn it is now working for you.

Thanks for that information. What you are describing is not possible using the Rank field (also known as LexoRank) as that is a non-numeric string of characters, which allows updates to ordering (including inserting issues in the middle of a list) without changing the Rank of surrounding issues. I have seen other community…

Hi @JuanD When you note it is not functioning as intended, what do you observe happening? Are you trying to synchronize the values, from the parent issue to be identical in the subtasks? If so, you can instead use the Copy from Parent issue option. If you are trying something else, would you please clarify. Perhaps if you…

Hi @Saqib Dar It is not possible to select a "board" with JQL. However... A board and backlog are views of issues based on a JQL filter. In addition, the column mapping of status values and Sprint (for scrum) impact what shows on the board. If you use that same JQL filter in your rule you can select the same resulting…

Hi @Apoorva Mallepally -- Welcome to the Atlassian Community! Short answer As you have concealed quite a bit of your dashboard image and query, it is unclear what is happening. I recommend you discuss this with your Jira site admin as you can show them the details of what you are trying and they can likely help. Longer…

Hi @Lindsey Abrahamsen You seem to be asking if an automation rule can create an issue in another project. That is possible, and you may select the project with the Create Issue action. If you are having challenges doing this, please post images of your complete automation rule and the audit log details showing the rule…

Hi @Scott Federman First thing: some of the advanced roadmap fields are not supported by automation rules. To learn if they are, find an example issue for your fields and use this how-to article to check: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ Next, I suspect those fields will…

Hi @技術事業群-資料中心營運處-維運整合部-維運一組Jameson_Liu Welcome to the Atlassian Community! Lookup issues is a set of issues, and not just one. Are you trying to send the list of issues to one person or each one to individuals? If you want one message for each, consider using a Branch on JQL rather than using Lookup Issues. Next,…

Hi @Oriyah Barzilay Would you please post images of your complete automation rule and the audit log details showing the rule execution? Those will provide context for the community to offer suggestions. Thanks! Until we see those... Are you trying to update each issue in the results of that JQL, or something else? There…

Hi @Albert Marti That action only appears to be available for Jira Service Management: https://community.atlassian.com/t5/Jira-Service-Management-articles/4-New-Form-Automation-Components-for-Jira-Service-Management/ba-p/2018674 You may want to contact Atlassian Support directly to learn if there are other options or plans…

Hi @Boyd Hong The compareTo() function returns -1, 0, or 1, indicating the ordering of the dates: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ If you want the days difference, please use the diff() function instead: {{now.diff(issue.customfield_10304).days}} Kind regards, Bill

Hi @Boyd Hong I believe that became configurable with the new issue views. I'm using a free Jira install now and so cannot test that as it has fewer custom field settings for configuration. Please see these two items to learn more about this: https://jira.atlassian.com/browse/JRACLOUD-75629…

Hi @Charles Liss Would you please post an image of what you are seeing? That may provide more context for the community to offers ideas. Thanks! Kind regards, Bill

Hi @Quang Nguyen Have you tried to use the change log and compare the differences in field length, before and after? Then use an advanced compare condition to check against your threshold value. For example: {{#=}}{{#changelog.description}}{{fromString.length()|0}}-{{toString.length()|0}}{{/}}{{/}} And here are some…

I tried this with Jira Cloud, so I wonder if there is a difference as you are using Jira Server, correct? Let's try writing this to the audit log to see if you see the expected values: {{#issue.components.name.left(1).toUpperCase().distinct}}{{.}}{{/}} The result should be the list of just the expected first characters,…

Hi @Osaid Khilfeh -- Welcome to the Atlassian Community! For a question like this, please post images of the following to provide context. That will help the community offer better suggestions. * single image of your complete rule * image of the specific action(s) where you are setting the description field * image of the…

Hi @Marc Thomson The due date field is a date type and your custom field is a date/time field, so instead try setting the field with this, using the jiraDate formatting to drop the time: {{issue."Change Date/Time".jiraDate}} And also, smart values are name, spacing, and case-sensitive. Let's confirm you have the correct…

Fascinating...It is not removing them but they are off the field view on the page! I believe if you click on the field and select all, you will find them off to the right side. There is something happening due to the use of the stringBefore() function, the iterator, and the extra carriage returns/line feeds you have in the…

First thing, smart value expressions can be built up from simple pieces. And something what seems like a complicate mess can be explained. That was a disclaimer for what follows... Your revised goal is to find the distinct first letters of the component names, and use them to select your tokens/indicators to add to the…

In my experience, one key to managing WIP / WIP aging is tight feedback loops. At every standup, help the team understand why more is pulled when stuff is in-progress already. And at the retro, take a longer look at any "WIP debt" that occurred.

Yes, that is a more complicated approach. And... In my experience, using automation rules requires learning, experimentation, and documentation. Unfortunately that last one is tricky given current capabilities of rules. A work-around is to document rules outside of the project, such as in Confluence. I also save my rules…

Hi @Adam_Sterrie To do this from inside of Jira, you could export the list of users from admin user management, sort/filter the resulting CSV file by last accessed (by product as needed), and then use email addresses for your contact list. I believe you could also call the REST API to gather this same information to do the…

Hi @Randy O'Neal First a disclaimer: I am just a user and do not work or speak for Atlassian or any marketplace vendors. With that out of the way... Addons like Great Gadgets are helpful for going beyond the built-in measures. I have used them for a while with some success. There is a feature of their gadgets which allows…

Hi @Franco Genga -- Welcome to the Atlassian Community! Please try using the split() function to split the text into a list: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#split-String-separator- If that does not help, please post images of your complete rule and the audit log details…

Sounds good, and my understanding is... * Rules defined at a global scope are counted against the limit, even if they only impact one project. * Rules defined at a project scope do not. I am trying to find out if the "Service Limits Breached" trigger can detect this. If it does, it may be helpful to have a global rule with…

Hi @Claire Smith Adding to Stephen's answer... You appear to be using a Standard license for Jira Cloud. Is that correct? If so, please note there are limits for global / multi-project rule executions per month, as explained below. And your rules seem to use very simple triggers, and so could trigger quite often and…

Hi @Daniel Schoeneck and the community helping on this one! You do not state the format of your epic name, so let's assume it is something like this: EPICNAME [0 to many component indicators, prefixed by " #"] Have you considered doing this in one step / edit action (without any conditions), using smart value list…