Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-1301

JEP-3 - Add optional "Released as" and "Stage Release" states to JIRA

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: In Progress (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: jira
    • Labels:
      None
    • Epic Name:
      JEP-3 - Add optional "Released as" and "Stage Release" states to JIRA
    • Similar Issues:

      Description

      As a Jenkins user and contributor, I sometimes have difficulties when I need to understand in which release the fix is available. GitHub commit links from the bot help much, but it requires extra time to navigate across commits and UI. In Jenkins core, Remoting and my plugins I would like to make it more explicit:

      I propose to...

      1. Modify workflow in the JENKINS project:
        1. Add a "Stage Release" state (or whatever similar name)
        2. Instead of "In Progress" => "Resolved", contributors can move integrated fixed into the "Stage Release" state.
        3. It may be helpful for components which do not release the integrated fixes immediately (e.g. Core, its modules, Remoting, Stapler, Blue Ocean, other plugins)
      2. Add an optional "Released As" field to JIRA (type=String)
        1. When a contributor moves the issue to "Stage release", "Resolved" or "Closed" state, an optional field appears in the dialog
        2. If the field is non-empty, it will appear in the ticket header, hence users won't need to look into comments and commit histories

      This proposal could improve contributor and user experience, but the proposed change is opt-in.

      It does not make the field/state mandatory, hence the existing flows won't be affected if the maintainers do not want to spend time on JIRA updates

        Attachments

          Issue Links

            Activity

            oleg_nenashev Oleg Nenashev created issue -
            oleg_nenashev Oleg Nenashev made changes -
            Field Original Value New Value
            Assignee R. Tyler Croy [ rtyler ]
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "Page (Jenkins Wiki)" [ 17459 ]
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "Proposal Text (Web Link)" [ 17460 ]
            oleg_nenashev Oleg Nenashev made changes -
            Remote Link This issue links to "Discussion in the ML (Web Link)" [ 17461 ]
            oleg_nenashev Oleg Nenashev made changes -
            Description As a Jenkins user and contributor, I sometimes have difficulties when I need to understand in which release the fix is available. GitHub commit links from the bot help much, but it requires extra time to navigate across commits and UI. In Jenkins core, Remoting and my plugins I would like to make it more explicit:

            I propose to...
             # Modify workflow in the JENKINS project:
             ## Add a "Stage Release" state (or whatever similar name)
             ## Instead of "In Progress" => "Resolved", contributors can move integrated fixed into the "Stage Release" state.
             ## It may be helpful for components which do not release the integrated fixes immediately (e.g. Core, its modules, Remoting, Stapler, Blue Ocean, other plugins)
             # Add an optional "Released As" field to JIRA (type=String)
             ## When a contributor moves the issue to "Stage release", "Resolved" or "Closed" state, an optional field appears in the dialog
             ## If the field is non-empty, it will appear in the ticket header, hence users won't need to look into comments and commit histories

            This proposal could improve contributor and user experience, but the proposed change is opt-in.

            It does not make the field/state mandatory, hence the existing flows won't be affected if the maintainers do not want to spend time on JIRA updates
            rtyler R. Tyler Croy made changes -
            Remote Link This issue links to "Page (Jenkins Wiki)" [ 19874 ]
            rtyler R. Tyler Croy made changes -
            Remote Link This issue links to "Page (Jenkins Wiki)" [ 17459 ]
            oleg_nenashev Oleg Nenashev made changes -
            URL https://github.com/jenkinsci/jep/tree/master/jep/3
            Assignee Oleg Nenashev [ oleg_nenashev ]
            Priority Minor [ 4 ] Major [ 3 ]
            Summary Add optional "Released as" and "Stage Release" states to JIRA JEP-3 - Add optional "Released as" and "Stage Release" states to JIRA
            oleg_nenashev Oleg Nenashev made changes -
            Issue Type Improvement [ 4 ] Epic [ 10001 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Name JEP-3 - Add optional "Released as" and "Stage Release" states to JIRA
            oleg_nenashev Oleg Nenashev made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child INFRA-1506 [ 188528 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child INFRA-1507 [ 188529 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child INFRA-1508 [ 188530 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child INFRA-1509 [ 188531 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child WEBSITE-473 [ 188532 ]
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue blocks INFRA-1505 [ INFRA-1505 ]
            orrc Christopher Orr made changes -
            Link This issue is duplicated by INFRA-969 [ INFRA-969 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child INFRA-1522 [ 188887 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child INFRA-1523 [ 188888 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child INFRA-1543 [ 189269 ]
            oleg_nenashev Oleg Nenashev made changes -
            Epic Child INFRA-1665 [ 191467 ]
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ]
            Hide
            danielbeck Daniel Beck added a comment -

            Oleg Nenashev Is this resolved?

            Show
            danielbeck Daniel Beck added a comment - Oleg Nenashev Is this resolved?

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              oleg_nenashev Oleg Nenashev
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: