Hi, I give you our scenario:
      I created (not started) a sprint where an issue "a" is planned (assigned to me). This issue is linked to an issue "b" which is assigned to another one and is planned in another sprint. The other sprint (with issue "b" in it) was started. When I start my sprint (with issue "a" in it) the sprint with issue "b" is automatically completed and all issues fall back to backlog.
      Is this a known bug or are we doing something wrong? But even when we doing something wrong, there should be a message or any warning before deleting another sprint.
      I don' know if it is relevant but we are using a custom field named "target group" where we identify the team which handles the issue.
      Greets Riccardo.

            [JSWSERVER-6837] sprint kills other sprints

            RenjithA added a comment -

            Hi Ricardo,

            I have moved this issue to be handled under Atlassian Support and you can see the new issue created in the linked issues section.

            We will provide you with our response in the new issue created. I am proceeding to close this issue.

            Cheers,
            Renjith

            RenjithA added a comment - Hi Ricardo, I have moved this issue to be handled under Atlassian Support and you can see the new issue created in the linked issues section. We will provide you with our response in the new issue created. I am proceeding to close this issue. Cheers, Renjith

              Unassigned Unassigned
              c38a42400628 Riccardo Salzer
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: