Hello, we are currently facing a problem. Jira issue change operation, the verifier judges the change fields. If it is a key field change, create a new issue in the custom script and block the current issue change operation. However, during the testing process, it was discovered that a new issue creation operation was triggered and the log printing was successfully created. But the new issue was not found. May I ask what the reason is?
@瑞祥 陈 - hi!
Can you let us know more?
I see one of your challenges is that you can't find the newly-created issue.
We are using Jira Data Center, The newly created issue key has also been queried. Postman calls the interface to query and returns' Issue Does not Exist '. I think it's because the issue modification window's submission operation was blocked, which caused the rollback of the operation data
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.