Non-Functional Requirements (Qualities) in GreenHopper

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Answered
    • None
    • Component/s: None
    • None

      As User, I want to be able to manage a Non-Functional Requirements (NFR) in GreenHopper agile board:

      • NFRs define a qualities of a product, which is not a behavioral requirements (User Stories)
      • One NFR can be referred by several User Stories. It means, that each User Story must conform (or is constrained by) NFR's terms
      • One User Story may refer to several NFRs. It means, that this User Story must conform (or is constrained by) all terms of all NFRs
      • NFRs must not be in backlog
      • NFRs must not have Assignee and Resolution fields. (I'm not sure, maybe some else fields). Instead they must have a validity period of time. This period defines, which Releases or Issues is affected by NFR's terms in some time interval.
      • There should be a UI zone on the GreenHopper agile board to manage NFRs. As an example - Epics panel. Something congenial.
      • There should be a list of NFRs for each User Story in Issue Detail View on the right side of agile board, well recognizable by a User. It must draw his (her) attention: "There are some requirements beside User Story description".
      • There should be an ability in Issue Detail View:
        • To access NFR's details
        • To remove NFR
        • To add new NFR
      • There should be an ability to view all User Stories referring to specific NFR

      Also, please refer to this support discussion GHS-7315

            Assignee:
            Unassigned
            Reporter:
            Dan Shebunin
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: