Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-17782

Allow to delete a step from an active workflow if there are no issues in that step

XMLWordPrintable

    • 2
    • 1
    • 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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      in a draft workflow i can not delete a step altough no issu has the status of the step.
      i can not add a new transition to the problematic step.

      you can see what i mean in the screenshot.
      for a new added step there are all the options. for the step i want to delete there i miss the options.

      regards,
      michael

        1. workflowbug.png
          workflowbug.png
          7 kB

            [JRASERVER-17782] Allow to delete a step from an active workflow if there are no issues in that step

            Franky Deleu added a comment -

            I am not able to add a new transition to an existing workflow.
            When I want to publish the workflow, JIRA says that you cannot add a transition to an active workflow.
            I'm stuck.

            Franky Deleu added a comment - I am not able to add a new transition to an existing workflow. When I want to publish the workflow, JIRA says that you cannot add a transition to an active workflow. I'm stuck.

            Deleted Account (Inactive) added a comment -

            How is the progress on this? Still not planned? We're updating our workflows and get a lot of orphaned steps as we decide to not use them anymore.

            BTW it should not be a problem to delete the step on an active workflow for the reasons you stated if there are no incoming transitions to the step, right? In that way nobody would transition issues to that step...

            Deleted Account (Inactive) added a comment - How is the progress on this? Still not planned? We're updating our workflows and get a lot of orphaned steps as we decide to not use them anymore. BTW it should not be a problem to delete the step on an active workflow for the reasons you stated if there are no incoming transitions to the step, right? In that way nobody would transition issues to that step...

            GilK added a comment -

            How do I deactivate a workflow?
            Thanks,
            Janiv.

            GilK added a comment - How do I deactivate a workflow? Thanks, Janiv.

            Michael Michael added a comment -

            Yes, problem exists in 4.2.1 and 4.2.2, too! I had an Support Request for that: https://support.atlassian.com/browse/JSP-69581 . There you can find a small video to reproduce this in a fresh installation. Please fix that soon as it is basic to be able to add Transitions to Workflow steps in Draft mode. I guess issue is related to the (closed) issue http://jira.atlassian.com/browse/JRA-15964 .

            Michael Michael added a comment - Yes, problem exists in 4.2.1 and 4.2.2, too! I had an Support Request for that: https://support.atlassian.com/browse/JSP-69581 . There you can find a small video to reproduce this in a fresh installation. Please fix that soon as it is basic to be able to add Transitions to Workflow steps in Draft mode. I guess issue is related to the (closed) issue http://jira.atlassian.com/browse/JRA-15964 .

            JoachimA added a comment -

            Looks like this problem is also happening in JIRA 3.13 until JIRA 4.2.1.

            JoachimA added a comment - Looks like this problem is also happening in JIRA 3.13 until JIRA 4.2.1.

            Nancy Belser added a comment -

            Any progress on this request? I accidentally added a status/step in my production workflow (thought I was in the test environment) and cannot get rid of it. The only way I can get rid of it is to deactivate the workflow, which will take MANY hours as I have 28 projects using this workflow and one of the projects has 75000 issues! This step has no transitions and essentially is an orphan since I also can't ADD any transitions to it while the workflow is active.

            Nancy Belser added a comment - Any progress on this request? I accidentally added a status/step in my production workflow (thought I was in the test environment) and cannot get rid of it. The only way I can get rid of it is to deactivate the workflow, which will take MANY hours as I have 28 projects using this workflow and one of the projects has 75000 issues! This step has no transitions and essentially is an orphan since I also can't ADD any transitions to it while the workflow is active.

            AntonA added a comment -

            I see what you mean. This is the current limitation for editing active workflows. The main reason it exists is concurrency - i.e. even if no issues exist on the step at the moment, in 0.001 of a second an issues could be created or transitioned into that step.

            We could still allow the edition to occur, and at the time of activating the workflow, do a check for existing issues, and if issues exist fail. We would then need to give the user an option to put the step back into the workflow (i.e. the existing step id needs to be used). Alternatively, the user can move the issues from the step and then try activating changes again.

            I will leave this issue open.

            For more information on the way new feature and improvement requests are scheduled, please see:
            http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

            Cheers,
            Anton

            AntonA added a comment - I see what you mean. This is the current limitation for editing active workflows. The main reason it exists is concurrency - i.e. even if no issues exist on the step at the moment, in 0.001 of a second an issues could be created or transitioned into that step. We could still allow the edition to occur, and at the time of activating the workflow, do a check for existing issues, and if issues exist fail. We would then need to give the user an option to put the step back into the workflow (i.e. the existing step id needs to be used). Alternatively, the user can move the issues from the step and then try activating changes again. I will leave this issue open. For more information on the way new feature and improvement requests are scheduled, please see: http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements Cheers, Anton

              Unassigned Unassigned
              f01eb8a9a9f4 Michael Kornatzki
              Votes:
              27 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated: