Dick Community Champion

Within the square brackets is the array of strings. In JSON format that would be something like ["string A", "String B", "String C"] that's why I removed the curly braces around your array elements. JSON format referral

Total should be: {"fields": { "fixVersions": [ {{#issue.fixVersions}}"id": "{{id}}",{{/}} "id": "{{version}}" ] }}

There's a couple of curly braces that I left out intentionally. Try the above please.

Hi Vincenzo, on hindsight, I see the {{/}} in your equation. Then you proceed with a comma, followed by your own version smart value {{version}}. You can let the automation log the {{#issue.fixVersions}}{"id": "{{id}}"},<strong>{{/}} </strong>"id": "{{version}}"<strong>part of the json. </strong>You want to see that you're…

Hi @vincenzo.spatafora the smart value in the example might be missing the closure tag: {"fields": { "fixVersions": [ {{#issue.fixVersions}}{"id": "{{id}}"},{{/}}{"id": "{{version}}"} <strong> {{/}}</strong> ] }}

Hi @Ivan Bilobrk , Best have two sets of statuses for the two flows. The step you take when changing the issue type could best be an automation (user triggered from the menu). That automation could also change the status to one of the statuses in your alternate workflow.

Hi @Sherwin Soriano Yes you can. As a precaution when doing bulk operations, you can export the selected issues first. If you need assistance with the automation, feel free to post a picture (with sensitive info censored). Sincerely Dick

Dear @Rita Belarbi , I think you've got your universes crossed here (though there is a specific resemblance to the Atlassian logo speaking in your favour :) ) You're on a Mac and the Keynote application is having difficulty updating due to some monetary issues related to your purchase and/or Apple account. Here, we're…

Hi Venkata, You would need a way to designate tickets to a certain client, then make sub-boards using filtering per client. You can use the component field to hold the client name, then make the sub-boards filtered by component = xyz Also you can have a master board where you use quickfilters to repeatedly preselect a…

Luckily for you, a board is just a pair of glasses to look at project(s) that hold the issues. You have to adjust your pair of glasses (meaning you have to configure the board correctly). Normally status "Open" is used for the backlog. In Kanban boards, configuration demands you to drag the open status in the backlog zone…

Thanks Bill, for stepping up. This surely helps. :)

Ah, MR is a Merge Request (sorry I didn't get that in the first place). If you're coupling merge requests to a ticket, the ticket key is usually used as the first part of the merge request name. From whatever tool you're using to integrate Git into Jira, you'll need to access the synchronized GIT repository in Jira from…

I now notice that Bill's line also seemed to be missing a closing parenthesis. With all the curly braces and parentheses, this can easily happen. So it's best to check using the above method to see if there is consistency in your formula's. 

Hi Gilad Thanks for elaborating a bit on the problem you're facing, makes it easier :) The error is about parenthesis not matching (and message you post clearly has a closing parenthesis missing). Looking at your math line, there's a discrepancy too: {{#=}}ROUND( (0+{{#lookupIssues}} double open…

well, you could start by sharing what you have now... maybe I can help out with syntax or by looking at your problem from a different angle. :)

Hi Gilad, Which part is giving you a headache? {{#=}} Start a calculation ROUND((0+ Round the number function {{#lookupIssues}} Iterate over the issues looked up by a jql statement {{#if Start a conditional statement (equals Look for equal parts A and B (status.statusCategory.name Part A, the status of the looked-up issue…

Hi Nirmal, Sometimes, one should look to a problem from the other side. In your case: * gather the list of MR's (whatever they may be, I have no clue here :) ) * check the list for non-merged MR's. * if this check yields you zero items, then set the status of the ticket to Done. I hope this will help you. Dick

you can log the above line (make visible what it parses and see if it matches what should be the "value" copied.

The essential part (the multi-value part) is in the hashtag # : And triggerissue has no capitals (no camel casing). The value parsed should imo be part inside the loop in object notation: {{value}} And the "human readable" name of the customfield should be used. And you should close the multi-value part with the slash:…

Hi Kelvin and Trudy, The multi-select variable yields a list of consecutive values as an answer. In order to tell Jira it has to work with a list during the copying to the destination issue, you need to use {{#issue.multivariable}} similar to Atlassian on smart values and lists So the edit process should definitively be an…

Hi AB and Trudy, The culprit of the automation is the left hand side of the equation: it should hold the name of the field (in this case being Team). The righthand side of the original equation of AB is right, there is no need to put .Id in the smartvalue.

Hi Drishti and Javier, I believe the smart value given by Javier shouldn't have the double quotes: {{#issue.Additional Items Required.value}} {{.}} {{/}} similar to {{issue. Story point estimate}} on the smart values page by Atlassian.

Hi Pashk, We're on DataCenter Jira, synchronising with AD using LDAP protocol. As accounts get deactivated, Jira is smart enough to provide a suffix to the user name: [x]. These users are not counted as having active licenses. As you're on Cloud Jira, things might be different, so I hope that someone with experience in…

Thank you for accepting my answer, it helps others find their way to solving similar problems. From your solution I see that you're on the newest version of Jira. At our datacenter Jira, we can't have for-children / for-children of children constructions nested. Happy Automations! Dick

Hi Aaron, I'm not familiar with the interface you're showing, but how about doing a release to clear the stuff that you've been doing from you board?

This works:

Hi Andrei, I've tested a similar query to yours. The linked issue statement highlighted in your picture is giving you ALL subbugs, since the first part doesn't restrict it to the parent issue you branched for. The name "Linked" is deceitful here, it refers to the two statements inside the step. As you always end up with…

You can process the name of issues into a variable, then use that variable to set the name in the proper form (without the "clone of") More on string manipulation by Atlassian More on variables by Atlassian I hope this will help you Dick

Check the contents of the storypoint field first. If a diligent user fills the field during creation, he would not be pleased seeing his/her value been overwritten by 1. Just my 2 cts :)

When I saw you request, @Aislin Percival, I became a bit saddened that your employer isn't willing to invest in your education. I hope that you find the time and space to learn by doing. Be aware that much of the specifics in Jira originate from the Agile Scrum manifesto. Some attention to that would certainly benefit your…