Basic Approval Steps In Feature Workflow

We all want to to be following an Agile process and Aha! in conjunction with JIRA allow us to do this. However, we need to do Agile with an element of control around key stage gates of the lifecycle of a Feature since we have to maintain our ISO certification and we need to pass audits from certain key customers in certain markets - Pharma and Defence are prime examples - these want to see control in place at key stage gates.

We have the following steps in our Feature Workflow:

Systems Engineering->Engineering Backlog->Release Backlog

We need to sign-off the transition from Systems Engineering to Engineering Backlog between the primary stakeholders of PM, Development & Architecture - this represents a Draft requirement in our SDLC and we need to sign-off the transition from Engineering Backlog to Release Backlog with a wider set of stakeholders such as QA as this represents a fully defined, estimated and resourced feature Committed to be delivered in the release.

We currently use a sign-off block in the Feature description combined with the addition of the comments "Approved for Engineering Backlog" , "Approved for Release Backlog" from the required signatures at these two stage gates.

It would be great if some kind of simple (optional) approval process like this could be configured within the Feature Workflow.

  • Roger King
  • Mar 15 2017
  • Unlikely to implement
Release time frame
  • Mar 23, 2017

    Admin Response

    Thank you for your idea. We do have a lot of flexibility with our workflows and the ability to customize them to your specific products and processes, so one option would be to add approval steps directly to the workflow. 

    Given the flexibility with workflows and options such as the one you have currently implemented we don't have plans to make changes in this area at this time. 

  • Attach files
  • warren lester commented
    July 05, 2017 08:17

    In many organizations that also follow forms of Agile development, stakeholder or executive approval is necessary at various key stages in the project process especially at the Vision stage. An approval process could follow the principle that Notebook creators can assign approvers when one is published and if rules are specified: Unanimous or Majority, the approval criteria could be recorded in the system.


    Ideally, variance from this approved vision should be visible in each child element; features, requirements etc. in order that progress towards the vision can be easily seen. 

  • Roger King commented
    July 24, 2017 15:40

    I don't think you follow my requirement. I want to be able to control moving from one state to another based on a configured list of stakeholders having pressed the Approved button or something similar.