Comments
-
Hi, Thank you. I'll test the solution and get back to you. Best regards,
-
@Luka Hummel - codefortynine Thank you for your suggestion, but we are looking for a solution using JMWE, as mentioned in the title of my post
-
@Trudy P Claspill @Kristian Walker _Adaptavist_ thank you so much for your answer it worked. I set up a script in script runner behavior which allows me to do that.
-
Hi @Trudy P Claspill @Ramez Kaupak @Simh Simh , Me too I am waiting for the solution to this problem. I noticed that this error only comes from numeric fields. Thanks, Reda
-
Hi @Bill Sheboy No its not Work . in the same issue Parent if I create a sub-task A the value OP-1 and a subtask B it always sets the value as OP-1
-
Hi @Bill Sheboy Thank you for your prompt response and detailed instructions I followed the instructions provided, but it's still not incrementing correctly. Every time I create a sub-task, it always sets the value as OP-1.
-
Hello everyone @Bill Sheboy @Trudy P Claspill @Matthew , and thank you for your insights. First, I'll be sharing my automation rule with you shortly to provide a clearer understanding of my current configuration. Automation Rule Steps: 1-Trigger: Ticket Created The rule is executed when a ticket is created. This trigger…
-
Hi @David Fischer Thank you so much for your assistance. It's working perfectly now. I truly appreciate your help.
-
Hi @David Fischer , Thank you for your guidance earlier. I tried implementing your suggestions, but I'm still facing issues. Firstly, I'd like to clarify that the field issue.fields.customfield_10109 is a dropdown list. Therefore, I'm using issue.fields.customfield_10109.value to fetch its value, else it returns an object.…
-
Hello @David Fischer , Thank you for your prompt response and detailed instructions. I've followed the steps you provided, but I'm encountering some issues. Firstly, although the task is created as expected, the linkage between the task and the epic doesn't seem to be working correctly. Moreover, when the epic doesn't…
