Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-7914

Jira issue type descriptions do not match RFC-43

    XMLWordPrintable

    Details

    • Story Points:
      1
    • Team:
      SQuaRE

      Description

      The online descriptions of the available issue types read:

      • Epic: Created by JIRA Agile - do not edit or delete. Issue type for a big user story that needs to be broken down.
      • Story: Created by JIRA Agile - do not edit or delete. Issue type for a user story.
      • Bug: A problem which impairs or prevents the functions of the product.
      • Improvement: An improvement or enhancement to an existing feature or task.

      However, RFC-43 specifies more specific definitions within the context of LSST:

      • Story: the result of breaking down a large task derived from the software development roadmap (LDM-240) – an epic, in other words – into workable units
      • Bug: a fault or error in code which has already been accepted to master
      • Improvement: a feature request or enhancement which has not been derived by breaking LDM-240 down into epics

      It would be helpful if developers could see these descriptions in Jira, rather than the defaults.

        Attachments

          Issue Links

          relates to

          RFC - An issue whose primary purpose is to advertise an intent and allow stakeholders to comment. RFC-43 Semantics of JIRA issue types

          • Implemented
          mentioned in

          Page Loading...

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            tjenness Tim Jenness added a comment -

            The relevant documentation is now in https://developer.lsst.io/processes/workflow.html#tickets (rather than the RFC).

            Show
            tjenness Tim Jenness added a comment - The relevant documentation is now in https://developer.lsst.io/processes/workflow.html#tickets (rather than the RFC).
            Hide
            Permalink
            swinbank John Swinbank added a comment -

            I'd be nervous about changing some of these, given the “do not edit” warning. I agree that the current situation is unfortunate, but I'm not sure that it's worth spending significant time to address it.

            Show
            swinbank John Swinbank added a comment - I'd be nervous about changing some of these, given the “do not edit” warning. I agree that the current situation is unfortunate, but I'm not sure that it's worth spending significant time to address it.

              People

              Assignee:
              frossie Frossie Economou
              Reporter:
              krzys Krzysztof Findeisen
              Watchers:
              Frossie Economou, John Swinbank, Krzysztof Findeisen, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:

                  Jenkins

                  No builds found.