• Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • None
    • Approvals, Next-gen
    • None

      Summary

      When you are adding an approval step to a next-gen project, it allows you to create a field instead of using an existing one. When you create that field, it is not possible to delete it afterward. If you run a GET in the fields, the approver field can still be seen after deleting the approval step.

      Environment

      Approval step on next-gen workflow.

      Steps to reproduce

      1. Create a next-gen project;
      2. Add an approval step in the workflow, creating an approver field to it;
      3. Delete the approval step;
      4. Run the Get fields API:
        curl -D- -X GET \
          --url 'https://instance.atlassian.net/rest/api/3/field' \
          --user 'email:token' \
          --header 'Accept: application/json'
        

      Expected results

      The approver field shouldn't be there anymore since I deleted the step from the workflow.

      Actual result

      The field will still be shown there and there is no way to delete it.

      Workaround

      Raise an issue with the support here mentioning this bug.

              Unassigned Unassigned
              esantos@atlassian.com Eduardo Santos
              Votes:
              8 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated: