Details

    • Similar issues:
      KULRICE-9613Document performance best practices in KRAD Guide
      KULRICE-9651Document performance best practices in KRAD Guide
      KULRICE-9525Document best-practices for using JPA with Kuali Rice
      KULRICE-378Document proper service location and dependency injection practices that rice client devs should use (do this during KRA retreat week - June 11)
      KULRICE-13562QA Cross-training: AFT failure analysis
      KULRICE-13573QA Cross-training: IT Failure Analysis
      KULRICE-13422QA Cross-training: AFT Gap Analysis
      KULRICE-13566QA Cross-training: Server installation and upgrade
      KULRICE-13539Document IT Failure analysis processes
      KULRICE-13783Document AFT Failure analysis processes
    • Rice Team:
      QA
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required
    • Code Review Status:
      Not Required
    • Include in Release Notes?:
      Yes

      Description

      Establish and document best practices for creating and maintaining Jiras. This is to ensure that we are all following similar practices, helping to keep Jira bloat to a minimum and making it easier to find and parse archived information.

      1) Search for duplicates before logging a new Jira. (Possible plugin to aid in this: http://www.plugenta.com/suggestimate/jira)
      2) Do not close Jiras with "backlog" for fix version; remove fix version entirely for "Won't Fix" Jiras.
      3) Each code commit should be tied to a Jira.
      4) Jiras should have significance to the team, should not be for individual task organization. (Suggested alternate organizational tool: Trello.com.)
      5) Summaries and descriptions should be written so they can be understood by all team members.
      6) Document progress, conversations, or impeding issues in comments.
      7) (Pending) Use new "Hindered" or "Impeded" status field for Jiras dependent on other Jiras.

        Activity

        Hide
        Adam Campbell (Inactive) added a comment -

        Discussed at leads meeting 10/4/13.
        Emailed help@kuali.org for new "Hindered" or "Impeded" status (cc'd Jessica).

        Show
        Adam Campbell (Inactive) added a comment - Discussed at leads meeting 10/4/13. Emailed help@kuali.org for new "Hindered" or "Impeded" status (cc'd Jessica).
        Hide
        Adam Campbell (Inactive) added a comment -

        Modifying existing Jira usage wiki entry: https://wiki.kuali.org/display/KULRICE/JIRA+Usage+Policy

        Show
        Adam Campbell (Inactive) added a comment - Modifying existing Jira usage wiki entry: https://wiki.kuali.org/display/KULRICE/JIRA+Usage+Policy

          People

          • Assignee:
            Adam Campbell (Inactive)
            Reporter:
            Adam Campbell (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Structure Helper Panel