We have created a behaviors for restricting fields if user select issue found In as Production and environment as pre -- production and also vise versa it should not be allowed. It is working fine . But if I'm cloning an issue I'm not able to restrict fields. Is there a way to restrict fields while cloning an issue.
Thanks.
Hi,
Behaviours can only restrict fields in the screen while creating or editing an issue (front-end). While cloning an issue the behaviour will not be applied. When editing the issue after cloning, the behaviours should apply again, if they are configured correctly.
If you want to have restrictions while cloning, you need to enforce some "back-end" checks by adding validators in the "Create" transition of your workflow.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @sravani vennapusa , thanks for your post.
When you use the word 'behavior', do you mean you are using ScriptRunner for this?
If so, I would go ahead and tag them and behaviours into this post so we can signpost more experts here.
Best wishes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.