Current Transition virtual field not working on global transition condition

[Aggelos Paraskevopoulos [Cententia]]

Hi,

is there any chance that "Current transition" virtual field is not returning any value when checked in a global transition?

I'm trying to write a condition like this:

"Only if the following boolean expression is true: %{Current transition} != %{Issue status}"

to avoid "seeing" the transition when in the same status.

Cheers/A.

[Fidel Castro Armario]

Hi @aggelosp,

I think that you should use "Target status" (field code %{00177}) instead of "Current transition", i.e., you should use:

%{00177} != %{00016}

where %{00016} si field code for Issue status.

[Aggelos Paraskevopoulos [Cententia]]

Hi @fcarmario ,

I've tried this and it's not working either.

Actually I've tried to get the "issue status" and append it to description in a post function and the value is empty.

[Fidel Castro Armario]

Please, confirm the version of JIRA and JIRA Workflow Toolbox you are using.

Can you, please, provide an XML export of your workflow?

[Aggelos Paraskevopoulos [Cententia]]

Latest JWT 2.2.44, tested with Jira 7.3.7 and 7.1.10.

Sending the XML export in a few. Please check the Acknowledged global transition.

A.

[Aggelos Paraskevopoulos [Cententia]]

    <action id="431" name="Acknowledged">
      <meta name="jira.description"></meta>
      <meta name="jira.fieldscreen.id"></meta>
      <restrict-to>
        <conditions type="AND">
          <condition type="class">
            <arg name="class.name">com.atlassian.jira.workflow.condition.UserInGroupCondition</arg>
            <arg name="group">exalate-automation-users</arg>
          </condition>
          <condition type="class">
            <arg name="expression">%{00177} != %{00016}</arg>
            <arg name="class.name">com.fca.jira.plugins.workflowToolbox.MathExpressionsCondition</arg>
          </condition>
        </conditions>
      </restrict-to>
      <results>
        <unconditional-result old-status="null" status="null" step="17">
          <post-functions>
            <function type="class">
              <arg name="class.name">com.atlassian.jira.workflow.function.issue.UpdateIssueStatusFunction</arg>
            </function>
            <function type="class">
              <arg name="class.name">com.atlassian.jira.workflow.function.misc.CreateCommentFunction</arg>
            </function>
            <function type="class">
              <arg name="class.name">com.atlassian.jira.workflow.function.issue.GenerateChangeHistoryFunction</arg>
            </function>
            <function type="class">
              <arg name="class.name">com.atlassian.jira.workflow.function.issue.IssueReindexFunction</arg>
            </function>
            <function type="class">
              <arg name="eventTypeId">13</arg>
              <arg name="class.name">com.atlassian.jira.workflow.function.event.FireIssueEventFunction</arg>
            </function>
          </post-functions>
        </unconditional-result>
      </results>
    </action>

[Fidel Castro Armario]

Yes, there is a bug. Global transitions are not considered. This will be fixed in next version of the add-on. I will provide a beta version as soon as possible.

[Fidel Castro Armario]

Hi @aggelosp. This issue has been fixed in version 2.2.45

[Aggelos Paraskevopoulos [Cententia]]

Appreciated. Thanks @fcarmario .