Jobs inside nested folders need to be activated after copying the top level folder

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      After copying a folder with a nested structure, like

      top1/
      level1/
      job1
      job2

      to a new folder top2 via "New Item", the jobs cannot be started (there's no "Build now") unless their configuration page was opened and saved once.

      This doesn't happen when the jobs are located at the top level, as in

      top1/
      job1
      job2

            Assignee:
            Unassigned
            Reporter:
            Dirk Heinrichs
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: