Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-1636

Workflow transition from "Any Status" to "Itself" visible in the workflow menu

    • Icon: Bug Bug
    • Resolution: Incorrectly Filed
    • Icon: Low Low
    • Trigger - Other
    • None
    • 1
    • Severity 3 - Minor
    • 3

      Issue Summary

      Configuring a workflow transition which allows "Any Status" to transition to "Itself" shows up for a fraction of a second in the Workflow menu before showing up under the Actions menu.

      Steps to Reproduce

      1. Create 2-3 transitions in a workflow which allows "Any Status" to transition to "Itself". For. e.g. Created three transitions from "Any Status" to "Itself" : "Transition 1", "Transition 2", "Transition 3"
      2. Setup an automation rule which will check the value of the "Assignee" field and if the status of the issue is "Open", it will transition it to "Assigned"
      3. Create a ticket and initially, it will be in the "Open" status.
      4. If you assign the ticket to anyone or yourself, the ticket will transition from "Open" to "Assigned" as per the automation rule.
      5. However, for a fraction of a second before the ticket transitions from "Open" to "Assigned", if we expand the workflow menu, we will be able to see the transitions "Transition 1", "Transition 2", "Transition 3" in the workflow menu.
      6. Once the ticket is transition to "Assigned", "Transition 1", "Transition 2", "Transition 3" will be visible under the "Actions" menu.

      Expected Results

      • "Transition 1", "Transition 2", "Transition 3" should not be visible under the workflow menu and should only be available under the "Actions" menu.

      Actual Results

      • For a fraction of a second before the ticket transitions from "Open" to "Assigned", if we expand the workflow menu, we will be able to see the transitions "Transition 1", "Transition 2", "Transition 3" in the workflow menu.

      Workaround

      Currently there is no known workaround for this behavior.

       

        1. Automation Rule.png
          Automation Rule.png
          131 kB
        2. Issue Replication.mov
          35.12 MB
        3. Workflow-2.png
          Workflow-2.png
          147 kB

            [AUTO-1636] Workflow transition from "Any Status" to "Itself" visible in the workflow menu

            Hey d74b08d0bd4c , the original GSAC ticket will be transferred by 46bc1338156a , it was not assigned to us so I didn't transfer it myself.

            Hwee Sen Wee added a comment - Hey d74b08d0bd4c , the original GSAC ticket will be transferred by 46bc1338156a , it was not assigned to us so I didn't transfer it myself.

            Hi ff96e0b1003e could you kindly share the link to the ticket that was transferred to the Bento team in order to further track the issue? thanks in advance and happy holidays!

            Daniel Ocando Espinoza added a comment - Hi ff96e0b1003e could you kindly share the link to the ticket that was transferred to the Bento team in order to further track the issue? thanks in advance and happy holidays!
            Hwee Sen Wee made changes -
            Resolution New: Incorrectly Filed [ 10100 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]
            Hwee Sen Wee made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Hwee Sen Wee made changes -
            Status Original: Short Term Backlog [ 12074 ] New: Needs Triage [ 10030 ]
            Hwee Sen Wee made changes -
            Comment [ The request being made is to 
            {quote}{{/rest/api/2/issue/<id>/transitions?sortByOpsBarAndStatus=true}}
            {quote}
            From Jira docs, [https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-issueidorkey-transitions-get|https://developer.atlassian.com/cloud/jira/platform/rest/v2/api-group-issues/#api-rest-api-2-issue-issueidorkey-transitions-get,]
            {quote}Returns either all transitions or a transition that can be performed by the user on an issue, based on the issue's status.
            {quote}
            Since the customer specifically created those self transitions in their workflow, this is expected behaviour. 

            However the transitions are being moved from the Status button into the Actions button, which is the customer's concern. 

             

              ]
            Hwee Sen Wee made changes -
            Status Original: In Progress [ 3 ] New: Short Term Backlog [ 12074 ]
            Hwee Sen Wee made changes -
            Development Effort New: M [ 13032 ]
            Status Original: Needs Triage [ 10030 ] New: In Progress [ 3 ]
            Gaurav Arora made changes -
            Component/s Original: Automation - Action - JSM [ 76101 ]
            Component/s New: Trigger - Other [ 70304 ]
            Key Original: JSDCLOUD-15627 New: AUTO-1636
            Project Original: Jira Service Management Cloud [ 18512 ] New: Automation for Cloud [ 22610 ]

            Hello all

            We use this feature for Jira Service Management and use it to trigger "Major Incidents" within our company. 

            Because we have an alerting to our board of directors in place, each accidental trigger causes a false positive message to the most influential people within our company. This behavior diminishes our products acceptance and therefore this bug is critical to us.

            Thanks for your understanding. 

            Kind regards, 
            Severin

            Severin Sutter added a comment - Hello all We use this feature for Jira Service Management and use it to trigger "Major Incidents" within our company.  Because we have an alerting to our board of directors in place, each accidental trigger causes a false positive message to the most influential people within our company. This behavior diminishes our products acceptance and therefore this bug is critical to us. Thanks for your understanding.  Kind regards,  Severin

              Unassigned Unassigned
              46bc1338156a Nishanto Das
              Affected customers:
              3 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: