Tim Kopperud Community Champion

Hi @Ethan Bhardwaj, great news. Thanks for accepting the answer. TimK

Hi @Ethan Bhardwaj, the JQL should be issue = CS-10 By your last image CS-10 seems to be the issue you are testing against, hense this is what we apply to the JQL. Try this, and test according to my previous reply. TimK Answering from mobile.

Hi @Ethan Bhardwaj, I don't have the solution yet, but we might get there soon. Can you, in the test rule (your image above) switch the rule trigger (green step) and replace it with Scheduled trigger? You can replace it by simply delete the existing trigger and add a new one. In that scheduled trigger: * set the JQL to…

Hi @Ethan Bhardwaj, sorry for my short reply yesterday, I was "PC offline", hence was not able to test accordingly, and replied from mobile. After testing it seems it works without using ".value" syntax. I do agree with @Bill Sheboy and @Dick that refetching the issue is important when you, within the rule, edit a field…

Hi @Ethan Bhardwaj , try using {{customfield_10037.value}} TimK 

Hi @Emna Elleuch, I first posted an answer here which I noticed had to be incorrect, hence I removed it. After trying to rephrase it and add a new example I still didn't get it, and I think its because I dont fully understand your requirements. E.g. when you are saying I've tried the attached rule for 1 sub task (that…

@Ethan Bhardwaj, since it seems you are using this rule for testing, I might recommend another approach for error investigation on smartvalues: * Make the rule as simple as possible * Use manual rule triggers, e.g. scheduled with a random long time span, using a selected issue like I have done below using issue MOBL-28.…

Hi @Ravina Jigyasi, thanks. Do you also have this? * provide some details (image) of an issue that you expect to see in the chart, but dont? TimK

Hi @Ethan Bhardwaj, can you provide the two things I mentioned in my first reply, now over-striked? Including the newly edited formula where you are using small caps. Also provide the result, i.e. the comment added. TimK

Hi @Jonathan Mandel, did you try implementing this, and did it solve your question? TimK

Hi @Abike Looi-Somoye, did you try implementing this, and where you able to solve this? TimK

@Ethan Bhardwaj, try small letters. customfield_xxxxx, not customField_xxxxx. TimK.

Hi @Ethan Bhardwaj, welcome to Atlassian community. Are you able to provide images of * the math formula, * the two field values used. That means from an issue where the two fields contain values, but are not working? Edited: I noticed later editions of the original question included this. TimK

Hi @Ravina Jigyasi, are you able to * show the JQL used in the filter HCM client issues? * provide some details (image) of an issue that you expect to see in the chart, but dont? You might conceal sencitive information by "blacking out" on the provided images. TimK

Hi @Ravina Jigyasi, welcome to the Atlassian community. Can you confirm that the resolved issues actually are set as resolved? That means having the resolution field set, and not only a status of category Done (green statuses). TimK

Hi @panjo, I now also tested using . (dot) in the group name, and it still works fine. TimK

Hi @panjo , where you able to get this to work? This worked for me: TimK

Hi @Spasimira Genova, if I understand you requirements correctly you will not be able to do this. A board column is mapped to one or more statuses. You cannot have tow columns using the same status. I had the same requirements a few years ago, and we solved it by adding the status, but the transition to this status was…

Hi @Patrice Champet, if I understand your requirement you might solve this by adding an automation rule for this. * The "accepted approval" leads to e.g. status A for all criticallities * In automation, define a rule that change the status to status B if the criticallity is not high. TimK

Hi @Fabio Scarvaglieri, welcome to Atlassian community. You are almost at the right place, that means you will find this within the Workflow editor. Your last image is from the Workflow editor, but you are on the wrong place. Click on the transition that leads to In progress, so it becomes "active" (I have in my example…

Hi @Jack Crowe, if you share some details on what started to fail after it worked I might be able to help further. TimK

I was able to reproduce the same error using set, and then got the rule to work replacing it with add. I did not test using . (dot) in the group name though (ref comment from @Marc -Devoteam- below). TimK

Hi @chris.ciccarello, thanks for accepting the answer. TimK

Hi @panjo, welcome to Atlassian Community. You might try to replace set with add, something like this: {"update": {"customfield_16209": [{ "add": { "name":"JG-Risk.Amsterdam" } }]}} TimK

Hi @chris.ciccarello, welcome to Atlassian community. If I understand your requirements correctly, you should use the Parent field. Epic link field is replaced with the Parent field. If the Epic field is on the create screen it will be displayed like this: Your admin might have removed it from the create screen to not…

Hi @Jack Crowe, if I understand you correctly you can apply something shown in the example below. Notice two things: * You will need to apply the rule scope accordingly to your requirements. * You must handle linking automation from both sides (hense bullet #1 above):* The linking is done while "standing" in the project…

Hi @Mireya Cintora, yes that is right. You cannot add any non-numbers to a number field. You might add something in the description for the field, that informs about the result in percentage. You might use a text field for this instead of number field even if it contains a number value. Though this is not working prefect…

Hi @Mireya Cintora, great it worked for you. And thanks for accepting the answer. To add the % at the end, try something like this: Which will give this result TimK

Hi @rtamam, there is possible to add fields to cards in Work Management, but currently not the Parent field though. The lack of Parent field is related to this feature request [JWMCLOUD-341] Add group by epic to board view - Create and track feature requests for Atlassian products. A workaround might be to create custom…

Hi @Mireya Cintora, if I understand your question correctly you might try something like shown in this formula: Which gives this result: So, for your rule you need to apply smart values for your custom fields into the ROUND() function, and further define the correct percentage formula. Something like this might work:…