Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-13143

Agile Simplified Workflow transition In Progress displays the post functions incorrectly

      Summary

      When creating a new Scrum Project, the transition In Progress shows post functions:

      The following will be processed after the transition occurs

      1. Type: class
        Class: com.atlassian.jira.workflow.function.issue.UpdateIssueFieldFunction
        Arguments:
        field.name = resolution
        field.value =
      2. Type: class
        Class: com.atlassian.jira.workflow.function.issue.UpdateIssueStatusFunction
      3. Add a comment to an issue if one is entered during a transition.
      4. Type: class
        Class: com.atlassian.jira.workflow.function.issue.GenerateChangeHistoryFunction
      5. Re-index an issue to keep indexes in sync with the database.
      6. Type: class
        Class: com.atlassian.jira.workflow.function.event.FireIssueEventFunction
        Arguments:
        eventTypeId = 13

      Environment

      • JIRA Software Scrum Default Workflow

      Steps to Reproduce

      1. Create a new Scrum project: "Scrum Software development" type
      2. Navigate to the Workflow
      3. View the *In Progress" transition post functions

      Expected Results

      Post functions display normally like on other transitions

      Actual Results

      They are showing unnecessary details

      Notes

      Workflow is still functional and can be edited.

            [JSWSERVER-13143] Agile Simplified Workflow transition In Progress displays the post functions incorrectly

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.06
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2849980 ] New: JAC Bug Workflow v3 [ 2936377 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2539977 ] New: JAC Bug Workflow v2 [ 2849980 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1545797 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2539977 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 1132697 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1545797 ]
            Kiran (Inactive) made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Kiran (Inactive) made changes -
            Link New: This issue is duplicated by GHS-11547 [ GHS-11547 ]

            Mauro Badii (Inactive) added a comment - - edited

            Found it occurring in JIRA Cloud 6.4-OD-16-006 and 7.1.0-OD-05-006

            Mauro Badii (Inactive) added a comment - - edited Found it occurring in JIRA Cloud 6.4-OD-16-006 and 7.1.0-OD-05-006

            Similar outcome as: JRA-45043

            Mauro Badii (Inactive) added a comment - Similar outcome as: JRA-45043

              Unassigned Unassigned
              mfernandezbadii Mauro Badii (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: