Cloning Job from one plan to another fails silently when it has artifact subscriptions

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Low
    • 6.5.0
    • Affects Version/s: 6.2.5
    • Component/s: User Interface
    • None
    • Severity 3 - Minor

      When you clone job from one plan to another Bamboo will detect that job has artifact subscriptions and fail. It is by design, because new job would not have access to artifacts from source plan.

      However:

      • there is no error message what went wrong making it very confusing for user (there is also no error in Bamboo logs)
      • after error occurs, list of jobs is never refreshed and always points to a current plan, no matter what is selected in source plan list
      • at first list of jobs is not sorted, after an error it's sorted alphabetically (it should be always sorted)

              Assignee:
              Pawel Skierczynski
              Reporter:
              Pawel Skierczynski
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: