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

Associate the Release button to a Workflow transition

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 3
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      It would be great if we can have an option to associate the Release button (link) from the Kanban board to a specific transition, so after release a version and add it to the issues, the issues can be closed or go to any other status.

      I also thinked about a Listener for that, but seems the Release button is not triggering any specific event.
      An event associated to this button can be a good approach as well.

          Form Name

            [JSWSERVER-11692] Associate the Release button to a Workflow transition

            Michel Duguay added a comment - - edited

            I would also like to have this feature (and also for Cloud)!

            Michel Duguay added a comment - - edited I would also like to have this feature (and also for Cloud)!

            James Black added a comment -

            We use a workflow of five status' which are mapped to a Kanban board:

            ToDo -> In Progress -> Testing -> Ready for Release -> Closed

            The Kanban board has the first four status' mapped to their own columns.
            "Closed" is not mapped because who wants to look at "Closed" issues?
            For us, this means that issues in the "Ready to Release" column are the ones to be released when we click the "Release" button.

            When the "Release" button is clicked; we fill out the necessary fields and accept.
            The issues are then cleared from the "Ready to Release" column.

            Our problem is that the issues are still mapped to the "Ready to Release" status and are not the "Closed" status.

            Can the "Release" button promote/modify issues?

            James Black added a comment - We use a workflow of five status' which are mapped to a Kanban board: ToDo -> In Progress -> Testing -> Ready for Release -> Closed The Kanban board has the first four status' mapped to their own columns. "Closed" is not mapped because who wants to look at "Closed" issues? For us, this means that issues in the "Ready to Release" column are the ones to be released when we click the "Release" button. When the "Release" button is clicked; we fill out the necessary fields and accept. The issues are then cleared from the "Ready to Release" column. Our problem is that the issues are still mapped to the "Ready to Release" status and are not the "Closed" status. Can the "Release" button promote/modify issues?

            ddalessandro added a comment -

            I'd like to have similar functionality but it seems that it would be easier for my purpose to: When a version is released that can trigger an event that I can tie to a workflow trigger.

            ddalessandro added a comment - I'd like to have similar functionality but it seems that it would be easier for my purpose to: When a version is released that can trigger an event that I can tie to a workflow trigger.

              Unassigned Unassigned
              aquadrospetry Andre Quadros Petry (Inactive)
              Votes:
              10 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: