Bill Sheboy Expert

Hi @KTulsankar -- Welcome to the Atlassian Community! First thing, for a question like this please post images of your entire rule and the audit log showing the details of the execution. That will provide context for the community to offer ideas. Next, you do not need a branch on Most Recently Created Issue to get the key.…

Hi @Christelle SIMON -- Welcome to the Atlassian Community! That is not possible for company-managed projects. Here is a suggestion to add the feature, matching what you described for the team-managed projects feature. You may watch/vote for it to see progress. https://jira.atlassian.com/browse/JSWCLOUD-22846 Kind regards,…

Hi @Mariam Jintcharadze An automation rule can run on a scheduled trigger, it can create an issue (e.g. story), and it can link issues to each other. However if you mean after you create all of the sub-tasks to then link them all to each other, that might be challenging due to potential timing issues in rules. You could…

Hi @Rafal_falisz -- Welcome to the Atlassian Community! What problem are you trying to solve, particularly with two different fields holding the same date value? What have you tried thus far to solve this problem? For a question like this, please post images of your rule and the audit log. This will provide context for the…

Hi @StnVikas Dhanorkar -- Welcome to the Atlassian Community! The rule images you posted do not seem to match the use case you describe. Perhaps try to find a screen grab extension for your browser which will grab the entire rule image by scrolling the view and then post that in one image. Also please note: this rule will…

For your use case of creating a formatted email, the only way I can think of is to instead set that body text to a different plain text, custom field, and then export to see what happens.

Agreed; that does seem like a helpful feature. The idea of separation by issue type seems to support these are different "work item types", and so the needed data and configuration could be quite different...or the same as in your use case.

Thanks for clarifying, and you would need to configure them separately by project. This is one of the advantages of the team-managed projects: individual configuration. I have not seen any suggestions like adding/managing shared screen configurations between team-managed projects, but you could add that suggestion.

Yes, and...remember to include the team formation things to jump start effectiveness / collaboration...and design the team t-shirt. There are lots of good ideas for this work in Liftoff: Launching Agile Teams & Projects by Diana Larsen and Ainsley Nies.

Hi @Yaron Shragai -- Welcome to the Atlassian Community! Do you mean the custom fields created in a team-managed project? If so, not yet, and...that development to make custom fields shared across company-managed and team-managed projects started work in February 2022. Please watch/vote for this item to see progress…

Eric, when you note "it does not work", what are you observing? The attributes should work out-of-the box. For a single-select field: * just the smart value returns the displayed value for the dropdown * .value also shows the display value * .value.asNumber provides the display value as a number if it is a valid number I…

Hi @Pawan Choure -- Welcome to the Atlassian Community! Such HTML features are apparently not supported, and you could submit a suggestion for Atlassian to add them. When I checked I did not find any open suggestions for this idea in the public backlog. I remember trying this same thing a while ago, and I just tried again…

Hi @Pavel Automation rules may not be a helpful to solve this reporting need, unless you are calculating to update a custom field and then reporting on that. I suggest drawing what you want as an example, and perhaps investigating marketplace reporting addons. Your note about there being "a huge amount of work" may make an…

Hi @Eric Bergeron As your field is a single-select, perhaps try adding the value attribute. {{issue.customfield_10088.plusDays(issue.customfield_10090.value)}} If that does not work, also add .asNumber Kind regards, Bill

Hi @Brad Johnston -- Welcome to the Atlassian Community! As already noted, the Lookup Issues action does not exist for the Server/Data Center versions of automation rules. I can think of a couple of work-arounds possible for the use case you described of summing the story points up to the parent epic: * the Server/Data…

Thanks for sharing that information, Craig. That training is an interesting introduction to agile ideas. I suggest viewers to review the original source materials after viewing this training, and to attend other training to help better understand/apply the ideas. Regarding the training, it could stand some improvements in…

Hi @Pedro HS Cunha The built-in gadgets have apparently not been improved/updated in more than a decade, so I suspect this is not a recent issue. More likely there is some ambiguity with your filter whereby the "Epic Link" field is not present for those issues. Would you please post your filter for some context? Thanks!…

Dan, I am out of ideas to suggest, and recommend submitting a ticket to Atlassian Support to learn what they can find. Looks like you are the site admin for a paid license, and so can do that here: https://support.atlassian.com/contact/#/

As you are trying to do work spanning multiple Jira projects, with a single team, which has support responsibilities, and applying some ideas from Jira's features for Scrum teams...I suggest talking to your Jira Admins about setting up a separate Jira project to pull data from the different projects (with a filter) and…

Did you first test the JQL with an example PR Number in advanced issue search? That will confirm the JQL is working before you try anything else. And, rather than using a branch, instead use the JQL with the Lookup Issues action. Then you can test the result in the condition.

Hi @aperezgt Adding to the ideas from @G subramanyam you may want to ponder some questions first, such as: What do you mean by "project"? Do you mean Project, like a defined goal/scope/plan/timeframe of work, or just a way to indicate a "feature"? Why are the people on the team working on multiple "projects" at one time?…

Hi @Tiago Pinheiro -- Welcome to the Atlassian Community! When you note "it does not work" what do you observe happening? Next, if you test that JQL manually with an known PR number, does it work as you expect? Finally, I would expect that JQL to return a lot of issues using NOT CONTAINS (!~) so perhaps: * instead try…

Hi @Jogibabu Merugumala Adding on to John's question, do you mean... When an issue is in the Developed status, And {{now}} is past the issue's Due Date, Then change the Priority to Highest. Kind regards, Bill

Would you please post an image of the edit action for your rule, as that may provide some context? That error does not appear to be related with the user picker, single user field you describe. Thanks! Regarding "why not field name", I suspect that the field name you entered in the JSON does not exactly match what the…

Hi @Robert Yataco Please take a look at the match() function with a regular expression to pull what you want: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#match-- For example: {{issue.description.match(".*[AREA](.*)[ENDAREA].*")}} If this could return multiple results, you will need to…

Hi @Heloisa Tiscoski In my opinion, there probably isn't a "best checklist app"...Instead there are ones in the marketplace which are better/worser fits for your team's needs. I recommend listing what you want such an app to do, and then review and try some of the apps. Also from what you describe, perhaps instead consider…

I am glad that helped, and... Did you note that you misspelled it as {{issuse.key}} as that was probably another problem?

Hi @Dimitrios Papadopoulos The {{createdIssue}} and {{createdIssues}} smart values apply for any issues you create while the rule is running: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--createdIssue-- To access the issue which triggered the rule, just use {{triggerIssue}} or just…

I am glad to learn that helped. Automation for Jira is frequently improving, and I hope that at one point the editor adds type-ahead autocomplete for smart values and/or validation on save with better error messaging to help find such things :^)

Yes, that sounds correct. Also it can help for complex queries to create them piece by piece, confirming the results as you go. Usually by adding the elements with AND clauses first and adding the OR ones later. Finally remember that AND takes precedence over OR, so when there is ambiguity in the JQL use parentheses to…