Issue Type Condition in Jira automation does not recognize Epics across Team managed projects

XMLWordPrintable

    • Severity 3 - Minor

      Problem

      The Issue Type Condition component in Jira automation does not recognize Epics across Team-managed projects. The issue here is that Epics in team managed projects have their own unique identifier. Need to treat these differently like we do for statuses.

      Environment

      Jira Cloud

      Workaround

      You can use the following workaround
      1. Add a Create Variable component just after the trigger with the following attributes:

        • Variable name: varIssueType
        • Smart value:
          {{issue.issueType.name}}

      2. Add an Advanced compare condition with the following attributes:

        • First value:
          {{varIssueType}}
        • Condition: does not equal
        • Second value: Epic

      This will allow you to compare based on Issue Type's name instead of just the Issue Type which has the bug. 

      Update

      This also might affect other issue types from Team-managed projects.

            Assignee:
            Unassigned
            Reporter:
            Simmo
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: