Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-35900

Move this project to the public Jenkins JIRA

    Details

    • Epic Link:
    • Sprint:
      1.0-m1, 1.0-japan-m9
    • Similar Issues:

      Description

      When we are going live we will need to move this project to the public Jenkins JIRA.

      Process will be

      1. Prepare this project for the move as per this article
      2. Import it into issues.jenkins-ci.org
      3. Move issues from the UX into Jenkins with the component "Blue Ocean"
      4. Delete the UX project on both JIRAs
      5. Create a new agile board
      6. Update notifications so they are sent to #jenkins-ux on freenode

        Attachments

          Activity

          Hide
          jamesdumay James Dumay added a comment -

          ping [~tcroy] is this what you would like to see happen?

          Show
          jamesdumay James Dumay added a comment - ping [~tcroy] is this what you would like to see happen?
          Hide
          jamesdumay James Dumay added a comment -

          I think there is some benefits to having our own project on issues.jenkins-ci.org

          Show
          jamesdumay James Dumay added a comment - I think there is some benefits to having our own project on issues.jenkins-ci.org
          Hide
          jamesdumay James Dumay added a comment -

          OK, component it is.

          Show
          jamesdumay James Dumay added a comment - OK, component it is.
          Hide
          jamesdumay James Dumay added a comment -
          Show
          jamesdumay James Dumay added a comment - Raised https://issues.jenkins-ci.org/browse/INFRA-725 for [~tcroy]

            People

            • Assignee:
              Unassigned
              Reporter:
              jamesdumay James Dumay
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: