Daniel Yelamos [Adaptavist] Expert

Hi Jesha I don't know how you have tried to solve this. Could you send us a part of your code? I am going to give it a try on my own to see if I can find a solution that works. Cheers!

Hello Danielle. I do not mind starting this discussion. However, I am a very young Computer Engineer so take any of this with a grain of salt. As I understand DevOps, it is spending a lot of time, to develop tools to be more comfortable. Before my current position at Adaptavist I was a DevOps engineer in Spain and before…

Hello Danielle. I do not mind starting this discussion. However, I am a very young Computer Engineer so take any of this with a grain of salt. As I understand DevOps, it is spending a lot of time, to develop tools to be more comfortable. Before my current position at Adaptavist I was a DevOps engineer in Spain and before…

If by change you mean that it does not get reset, then yes, it won't. That happens because it is a field behavior. If you want a reset on every form change, you should change the field behavior to an initializer. Please tell me if this helped. Cheers!

Hello Michael. That is happening because the @ needs to be in a new line. Your code should look like this: import groovy.transform.BaseScript@BaseScript FieldBehaviours behaviours Hope this helped out

Hi Fabian. You are right, it does not exist. However, you can access it by: def issueTypeManager = ComponentAccessor.getComponent(IssueTypeManager) Hope this helped! Cheers

Hello Michael This is the solution to what you are looking for: import com.atlassian.jira.component.ComponentAccessorimport com.onresolve.jira.groovy.user.FieldBehavioursimport groovy.transform.BaseScript@BaseScript FieldBehaviours behavioursimport static com.atlassian.jira.issue.IssueFieldConstants.*def varCheck =…

Hello Michael. Are these fields custom fields or not? It would change a bit the implementation of the code. If you give me a specific example of what you want I try my best to tell you how to do this. Cheers

Hello Peter. We have this logged in our support desk as a known issue. We are currently working on a fix for this. If you want to see the progress and status updates on the issue, here is the link so that you can watch it: https://productsupport.adaptavist.com/browse/SRJIRA-2107 Hope this helps!

It seems to be the exact same question Sam.

Hello Alan. I can verify that it is as you state and this has been added as a bug in the ScriptRunner log. Thanks very much. You can access the issue in the link below to check its status. https://productsupport.adaptavist.com/browse/SRJIRA-2212 It will be resolved in future releases. Cheers!

Hi Ron. Glad to run some testing for you. We checked out different jira versions, 7.3.0, and 7.3.3 and in both cases it worked. We realized that in your issue, we see that in the original question, you have: def issueKey = "JIRA-1234"; however, you say it does not work when: def issueObject =…

Hello. I have set up a test environment and it seems to work. I have attached this customlistener to every issue event. As you can see here: Could you tell us which event you are attaching the listener to so that we are able to give it a try? Cheers!

Hello Henrik: Could you please provide the code that you are using so that we have something to base our development on? Cheers!

Hello Roy: Seems like you took an example that was a bit outdated. I tried this on my machine and it worked fine. Feel free to give it a try and if you come up with any other issues feel free to ask again. import com.atlassian.jira.component.ComponentAccessordef customFieldManager =…

Hello Alan. As I understand you have two parts to your issue: Part A: the form calls the initializer on the field in the behaviour when you change another field: Part B: When the form is wrongly entered, such as when there is a required field missing, it calls the initializer again. For Part A: (the first import statement…

Did this solve your issue?