Test issue type being auto-added to Issue Schemes
Hey folks, Hoping this has an easy answer! I'm trying to create a new Issue scheme in Jira, with a single Issue Type (that isn't "Test") in it, but every time I new project that uses the scheme, the "Test" issue type has been added back into it. There's nobody else editing the scheme - is there any way to prevent this from happening?355Views1like0CommentsZephyr Test execution reindex failed:errorType":"ERROR","clientMessage":"We encountered some problem
Hi All, We recently came across this problem post successful migration from Jira server to Jira cloud with Zephyr App data. While following documentation for app data migration there is one step mentioned that you need to clear server cache from Zephyr configuration and perform Metadata reindex and Execution reindex. Metadata reindex works fine for migrated project while Execution Execution failing with below error: errorType":"ERROR","clientMessage":"We encountered some problems during processing this request. Please try again!","errorCode":111}" We have spent hours to figure out the issue and finally after comparing the project already exists which we can successful Execution reindex, cross verified the permission schemes for both project and identified the differences missing the addon role in migrated project, just add the role to permissions Administer project ,edit issues, browse permissions and solved the problem. Hope this will help those who struggle on last step during migration journey from server to cloud! If you still face issues let me know will try to help!963Views1like2CommentsReindex Failed For Test execution: errorType":"ERROR","clientMessage":"We encountered some problems"
Hi All, We recently came across this problem post successful migration from Jira server to Jira cloud with Zephyr App data. While following documentation for app data migration there is one step mentioned that you need to clear server cache from Zephyr configuration and perform Metadata reindex and Execution reindex. Metadata reindex works fine for migrated project while Execution Execution failing with below error: errorType":"ERROR","clientMessage":"We encountered some problems during processing this request. Please try again!","errorCode":111}" We have spent hours to figure out the issue and finally after comparing the project already exists which we can successful Execution reindex, cross verified the permission schemes for both project and identified the differences missing the addon role in migrated project, just add the role to permissions Administer project ,edit issues, browse permissions and solved the problem. Hope this will help those who struggle on last step during migration journey from server to cloud! If you still face issues let me know will try to help!750Views1like1Comment