Jira Service Management don't trigger notification in certain status

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible



Problem

When an issue is transition to certain status, Jira Service Management does not generate any notification. When user tried to transition the issue to the particular state, the following error shown in atlassian-jira.log:

2016-03-04 07:09:45,794 http-nio-8128-exec-8 ERROR admin 429x1292x2 1q47jn1 172.22.65.249 /rest/api/2/issue/50700/comment [c.a.jira.workflow.OSWorkflowManager] Caught exception while attempting to perform action 851 from workflow 61100 on issue 'HELP-7856'
com.opensymphony.workflow.InvalidActionException: Action 851 is invalid
	at com.opensymphony.workflow.AbstractWorkflow.doAction(AbstractWorkflow.java:559)
	at com.atlassian.jira.workflow.OSWorkflowManager.doWorkflowActionInsideTxn(OSWorkflowManager.java:825)
	at com.atlassian.jira.workflow.OSWorkflowManager.doWorkflowAction(OSWorkflowManager.java:786)
	at com.atlassian.jira.workflow.WorkflowTransitionUtilImpl.progress(WorkflowTransitionUtilImpl.java:348)
	at com.atlassian.servicedesk.internal.listener.LegacyCommentTransitionListener.com$atlassian$servicedesk$internal$listener$LegacyCommentTransitionListener$$performTransitionAction(LegacyCommentTransitionListener.scala:170)
	at com.atlassian.servicedesk.internal.listener.LegacyCommentTransitionListener$$anonfun$com$atlassian$servicedesk$internal$listener$LegacyCommentTransitionListener$$maybeTransition$3.apply(LegacyCommentTransitionListener.scala:111)
	at com.atlassian.servicedesk.internal.listener.LegacyCommentTransitionListener$$anonfun$com$atlassian$servicedesk$internal$listener$LegacyCommentTransitionListener$$maybeTransition$3.apply(LegacyCommentTransitionListener.scala:108)
	at scala.Option$WithFilter.map(Option.scala:207)
	at com.atlassian.servicedesk.internal.listener.LegacyCommentTransitionListener.com$atlassian$servicedesk$internal$listener$LegacyCommentTransitionListener$$maybeTransition(LegacyCommentTransitionListener.scala:108)
	at com.atlassian.servicedesk.internal.listener.LegacyCommentTransitionListener$$$$$$f1b4c5f5bf48dbf2ec9e5fdc5cd72d$$$$nonfun$apply$13$$anonfun$apply$15.apply(LegacyCommentTransitionListener.scala:94)
	at com.atlassian.servicedesk.internal.listener.LegacyCommentTransitionListener$$$$$$f1b4c5f5bf48dbf2ec9e5fdc5cd72d$$$$nonfun$apply$13$$anonfun$apply$15.apply(LegacyCommentTransitionListener.scala:93)

Diagnosis

From the log, it's shown that the error is caused by the workflow used by the issue. Checking the specific action id in the workflow exported to XML file will show the following:

        <action id="851" name="Test123" view="HELP Log Work">
          <meta name="jira.i18n.submit">sd.workflow.itsupport.transition.waitcus.submit</meta>
          <meta name="jira.description"></meta>
          <meta name="jira.i18n.description"></meta>
          <meta name="jira.i18n.title">sd.workflow.itsupport.transition.waitcus.title</meta>
          <meta name="jira.fieldscreen.id">10921</meta>
          <meta name="sd.action.key">sdWFSupportToWFCustomer</meta>


Cause

From the XML export of the workflow, there's 

<meta name="sd.action.key">sdWFSupportToWFCustomer</meta>

line shown. This property is used in Jira Service Management 2.5.X and has been depcrecated in Jira Service Management 3 and above. The depcrecated function block notification from being generated in Service Management 3.X


Resolution

Open every one of your transitions and remove the sd.action.key property :

  1. Open the Workflow that is used for your Service Management project.
  2. Edit the Workflow. Please open the editor in "Text" mode.
  3. Click on any of the transition.
  4. Click on "View Properties" as shown here : Test1.png
  5. Delete sd.action.key entry if you find it in any of the transition as shown here : Test2.png


Last modified on May 23, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.