Dick Community Champion

Hi @Ivan Manolov _Appfire_ I was tinkering further on the final solution and came across some minor bumps, which I'm mentioning here for all interested parties to read: * The domainCsv picked up a leading space. As the selectlist didn't hold entries with a leading space, I got an error. Using .trim() after the .split got…

A silver lining, but in the end falling flat on my face: * The correct issues are found using the webrequest. * The correct domains are found inside two arrays when polling the domain customField of these issues. * Then flatten in all it's combinations came along and wiped the content of the domain customField arrays. *…

Hi Ivan, It was your point 1: The call to the api had flaws. /rest/api/2/search?jql=%27parent%20link%27%20%3D%20{{MovementKey}} gives me the initiatives now properly using the log action with this message: Looked up issues = [ {{webhookResponse.body.issues.key}} ] I already added the Authorization and Bearer…

Tiny result Using: <our instance>/REST/API/3/search?jql=%27parent%20link%27%20%3D%20{{MovementKey}} gives me a Response 200 and a Request GET with the complete path The {{webhookResponse.body}} however contains a lot of stuff that isn't related to specific Jira Items. Even this came along: {{webhookResponse.body}}…

Hi @Ivan Manolov _Appfire_, A couple of things I would like to mention: * First: please say hello to Hannes from me :) We did some debugging on JXL together. * I need the value stored on the movement as I use it to gather Jira Items for displaying purposes, so I need to get the REST route working. * jql='parent link' =…

Going for the How to sum story custom filed values to an epic? solution using web request to the REST API mentioned in the comments by Bill. 

Ow bummer: Lookup issue action - Add support for more fields on JIRAAUTOSERVER-877 this should've been tackled for Jira Datacenter 3 years ago... My list is empty to begin with!

These pictures contain the test Gor asked. The parentheses after flatten are not making a difference. I'm now suspecting our underlying Java (openJDK-21). Kind regards, Dick

Hi there, @Lalithesh. It seems that you use Jira Cloud. I'm using Datacenter version 10.3.24 (indicated in the tags on the right). I'm sorry, but I'm not particularly looking for a confirmation that the solution works in Jira Cloud. Hi there, @Gor Greyan I noticed the extra parenthesis after flatten(), which were neither…

@Murray le Roux : The key was in the comment between brackets: it turned out that notepad embroydered my stored Jira solution with invisible mark-up that corrupted the xml. Direct bash to bash copy ensured that the (carefully typed-in Atlassian answer for Jira) also worked for Confluence.

I'm fully aware of that. 

I asked the same question to Atlassian Support. Shruthi Hebbal was so kind to point me in the good direction. The labelmanager functionality I needed can be obtained using the confluence API. She pointed me to Gist Spaces by User Category where user Malte Schmidt provided a working solution of a spaces list by category. I…

Hi. Labelmanager has been removed from supported Atlassian functionality. We updated to Confluence 9.2 and our custom macro to list spaces according to their category also borked.

Hi @andrea.kunz-ext The high-over initiatives are filled with contributions, the epics by different groups. I suppose you are in close communication with these groups as to coordinate their powers to get the best results for the goals you described in the initiatives. If you're already in communication with these groups,…

Hi @Laura Schulz Please be advised that although auto-scheduling can give you the insights into critical paths you're might need, by confirming such scheduling, you're actually saving the modified dates onto the Jira work items you're seeing in your plan. It would be wise to do this in a meeting with all project leads…

Hi @Priyanka Agrawal It seems you create the useraccountIDs variable inside the branch. That means that every time that an mfg is processed, this variable is re-made from scratch, so it loses the prior content. Creating this variable before entering this branch would be beneficial. Kind regards, Dick

Hi @Rebecca Atlassian has several useful pages on smart values, but none contain the function contains. The Jira Query Language offers the "like" operator, represented by a tilde: ~ You can automate processing issues and check them using a conditional statement based on the outcome of a query; issue.summary~"Hello" or…

Hi @Isabel Green Can you post a picture as to where you've put this key-value pair? This would help to pinpoint why it's not working for you. Kind regards, Dick

Drawing a Venn diagram is also useful to get a grasp on how operators like not, or and and work. Kind regards, Dick

Hi @Mohd Aamir Mir Welcome to the Atlassian Community Have you considered extracting the valuable information of the payload by means of smart value operations on texts provided by Atlassian? You can use indexOf(String str) to locate the key-value pair you're interested in. Then use substring(int start, int end) or one of…

@daniel.jones please provide all the configuration details of the individual steps of your automation as well.

Hi @daniel.jones There's a couple of potential pitfalls in your automation: * Branches fire in parallel, you do not know which will be executed first. * The result of a branch should be reached in the branch, not in consecutive statements on "the main line of execution" (the vertical grey lines mean something here!) * Your…

Hi @daniel.jones This second question (and even follow ups on that) could be prevented if you shared your whole automation, including the per-step configurations. Let's start by sharing the automation so that we can see what goes wrong? Kind regards, Dick

Hi @daniel.jones {{issue.summary}} is a smart variable that hasn't been set using a create-variable step. you can however use the field itself in the log by stripping the curly braces. Kind regards, Dick

Status changes can have an order. Their behavior is governed by adding the property opsbar-sequence (it's a key-value pair). It has been explained previously in this forums here: How-to-set-the-order-of-workflow-transitions The key is called opsbar-sequence and the allowed values are integers. Best keep the values a bit…

Because @Michael Wohlgemuth expected and dealt with all possible user inputs (also false ones), I voted for this solution. Well done, Michael! Kind regards, Dick

Hi @Manuel Bernardino Marques da Silva Welcome to the Atlassian Community. It would be wise to separate development from production in your case. If this is not possible for you, building trust between you and the developers would be the first step into overcoming your fear of edited issues. Kind regards, Dick

Do a lookupissues = for the different (parts of) JQL's you are using and list these in the automation log. It would reveal to you why you aren't seeing the right issues in the end. - People that use logging are perceptive of the fact that sometimes other people would need to look into their automations and actually…

You both are aware that the API search engine Lucene is being replaced and that there are new API end-points for initiating searches? It would mean that the people making the excel plugin would need to update as well. Kind regards, Dick

Elegant solution to free up your Jira System Admin! Kind regards, Dick