I make script listener in Scriptrunner which try to make issue transition on workflow. It works but in atlassian-jira.log I have ERROR with long stacktrace
I suppose the problem in Secure Fields plugin https://marketplace.atlassian.com/apps/1212681/secure-fields-data-security-privacy?tab=overview&hosting=server but can't understand how to fix it. There are no any secure fields on this workflow
year-m-d 18:01:36,738 http-nio-12-exec-87 INFO user xxx xxx IP, IP /secure/AjaxIssueAction.jspa [onresolve.scriptrunner.runner.ScriptBindingsManager] Set assignee as assigneeUser
year-m-d 18:01:36,777 http-nio-12-exec-87 ERROR user xxx xxx IP, IP /secure/AjaxIssueAction.jspa [utils.lucene.permission.SecureFieldLucenePermissionUtils] An error occurred during invocation of method getSearchPermissionRulesForIndex in SecureFieldLucenePermissionUtils
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor991.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.coresoftlabs.common.utils.lucene.permission.SecureFieldLucenePermissionUtils.getSearchPermissionRulesForIndex(SecureFieldLucenePermissionUtils.java:18)
at com.coresoftlabs.common.utils.lucene.indexers.SecureSortableTextCustomFieldIndexer.addDocumentFields(SecureSortableTextCustomFieldIndexer.java:62)
at com.coresoftlabs.common.utils.lucene.indexers.SecureSortableTextCustomFieldIndexer.addDocumentFieldsNotSearchable(SecureSortableTextCustomFieldIndexer.java:38)
at com.atlassian.jira.issue.index.indexers.impl.AbstractCustomFieldIndexer.addDocumentFieldsNotSearchable(AbstractCustomFieldIndexer.java:76)
at com.atlassian.jira.issue.index.indexers.impl.AbstractCustomFieldIndexer.addIndex(AbstractCustomFieldIndexer.java:102)
at com.atlassian.jira.issue.index.managers.CustomFieldIndexerAdapter.addIndex(CustomFieldIndexerAdapter.java:39)
at com.atlassian.jira.issue.index.indexers.FieldIndexerWithStats.addIndex(FieldIndexerWithStats.java:57)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory$Builder.add(DefaultIssueDocumentFactory.java:365)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory$Builder.addAll(DefaultIssueDocumentFactory.java:341)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory.lambda$createDocuments$2(DefaultIssueDocumentFactory.java:126)
at java.util.Collections$SingletonList.forEach(Collections.java:4822)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory.createDocuments(DefaultIssueDocumentFactory.java:125)
at com.atlassian.jira.issue.index.DefaultIssueDocumentFactory.createDocument(DefaultIssueDocumentFactory.java:96)
at com.atlassian.jira.issue.index.DefaultIssueIndexer$DefaultDocumentCreationStrategy.get(DefaultIssueIndexer.java:1304)
at com.atlassian.jira.issue.index.DefaultIssueIndexer$IssuesOperation.createDocument(DefaultIssueIndexer.java:977)
...
Caused by: java.lang.NullPointerException at com.coresoftlabs.secureFields.commons.config.base.permissionsSchemesForCustomFields.CustomFieldPermissionsSchemeConfigLinker.<init>(CustomFieldPermissionsSchemeConfigLinker.java:41) at com.coresoftlabs.secureFields.commons.config.base.permissionsSchemesForCustomFields.CustomFieldPermissionsSchemeConfigLinker.build(CustomFieldPermissionsSchemeConfigLinker.java:31) at com.coresoftlabs.secureFields.commons.config.base.permissions.PermissionssUtils.getSearchPermissionRulesForIndex(PermissionssUtils.java:145)
... 445 more
Moving tickets between JIRA projects is not very easy because the projects might have different fields etc. You will have to write a custom workflow post function to do it.
Most people pass tickets between users/groups in the same project during escalations (i.e. only the assignee and/or a group custom field value changes) and that can be done using existing workflow post functions out there.
There is also the jelly escalation done by Atlassian themselves.
For groups outside of JIRA, I have seen people using custom plugins. You might also want to look at JEMH plugin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you'd consider using a single project we use component based assignement and escalation. You can add a "escalate" transition that re-assigns to L2 teams. YOu can specify just who is available to assign at each level/component too.
https://marketplace.atlassian.com/plugins/com.edwardawebb.jira-assign-escalate



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.