JIRA Toolkit Auto Transition Listener fails due to InvalidActionException

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

症状

When the com.atlassian.jira.toolkit.listener.AutoTransitionListener executes, it fails with the below exception in the atlassian-jira.log:

2012-10-04 11:46:00,739 QuartzWorker-1 ERROR ServiceRunner    Create Comments - LLAMA LLAMA [atlassian.jira.workflow.OSWorkflowManager] Caught exception while attempting to perform action 3 from workflow 11500 on issue 'DUCK-12'
com.opensymphony.workflow.InvalidActionException: Action 3 is invalid
	at com.opensymphony.workflow.AbstractWorkflow.doAction(AbstractWorkflow.java:559)
	at com.atlassian.jira.workflow.OSWorkflowManager.doWorkflowActionInsideTxn(OSWorkflowManager.java:894)
	at com.atlassian.jira.workflow.OSWorkflowManager.doWorkflowAction(OSWorkflowManager.java:850)
	at com.atlassian.jira.workflow.WorkflowTransitionUtilImpl.progress(WorkflowTransitionUtilImpl.java:270)
	at com.atlassian.jira.toolkit.listener.AutoTransitionListener.workflowEvent(AutoTransitionListener.java:145)
	at com.atlassian.jira.event.issue.IssueEventListenerHandler$IssueEventInvoker.invoke(IssueEventListenerHandler.java:49)
	at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$2.run(AsynchronousAbleEventDispatcher.java:60)
	at com.atlassian.event.internal.AsynchronousAbleEventDispatcher$1.execute(AsynchronousAbleEventDispatcher.java:28)
	at com.atlassian.event.internal.AsynchronousAbleEventDispatcher.dispatch(AsynchronousAbleEventDispatcher.java:56)
	at com.atlassian.event.internal.EventPublisherImpl.invokeListeners(EventPublisherImpl.java:151)
	at com.atlassian.event.internal.EventPublisherImpl.publish(EventPublisherImpl.java:70)
	at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$AbstractMultiTenantAwareInvocationHandler.invokeInternal(MultiTenantComponentFactoryImpl.java:181)
	at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$MultiTenantAwareInvocationHandler.invoke(MultiTenantComponentFactoryImpl.java:211)
	at $Proxy5.publish(Unknown Source)
	at com.atlassian.multitenant.event.DefaultPeeringEventPublisherManager.publish(DefaultPeeringEventPublisherManager.java:17)
	at com.atlassian.multitenant.event.PeeringEventPublisher.publish(PeeringEventPublisher.java:23)
	at com.atlassian.jira.event.issue.DefaultIssueEventManager.publishEvent(DefaultIssueEventManager.java:124)
	at com.atlassian.jira.event.issue.DefaultIssueEventManager.dispatchEvent(DefaultIssueEventManager.java:102)
	at com.atlassian.jira.issue.util.DefaultIssueUpdater.doUpdate(DefaultIssueUpdater.java:88)
	at com.atlassian.jira.plugins.mail.handlers.AbstractCommentHandler.update(AbstractCommentHandler.java:204)
	at com.atlassian.jira.plugins.mail.handlers.AbstractCommentHandler.handleMessage(AbstractCommentHandler.java:153)
	at com.atlassian.jira.plugins.mail.handlers.CreateOrCommentHandler.handleMessage(CreateOrCommentHandler.java:98)
	at com.atlassian.jira.service.services.mail.MailFetcherService$1.process(MailFetcherService.java:361)
	at com.atlassian.jira.service.services.mail.MailFetcherService$MessageProviderImpl.getAndProcessMail(MailFetcherService.java:264)
	at com.atlassian.jira.service.services.mail.MailFetcherService.runImpl(MailFetcherService.java:349)
	at com.atlassian.jira.service.services.file.AbstractMessageHandlingService.run(AbstractMessageHandlingService.java:250)
	at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
	at com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
	at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
	at com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
	at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

原因

This can be caused by any of the following:

  1. The Action ID references an action that does not exist for the workflow of that issue.
  2. A workflow transition condition is not being met.
  3. A workflow transition validator is not being met.

ソリューション

  • Verify that the Action ID is valid for that issue and issue type.
  • Check the workflow conditions are met for the user making the change to the issue (the transition). 
  • Confirm the user is meeting the workflow validators for the transition.
(info) For example, if the listener has been configured to re-open an issue from an email, the user commenting on the issue will execute the transition, and as such will require the appropriate conditions and will also need to meet the validators of that workflow transition.
最終更新日 2016 年 3 月 30 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.