• Type: Bug
• Resolution: Duplicate
• Priority: Low (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: 8.0.0, 8.20.0, 9.0.0, 9.4.0, 9.11.0
• Component/s: Scrum Board, Sprint
• Labels:

  None

1. Step1.png

   06/Sep/2023 7:29 AM

   267 kB

   Julien Rey

2. Step2.png

   06/Sep/2023 7:29 AM

   120 kB

   Julien Rey

3. Step3.png

   06/Sep/2023 7:29 AM

   233 kB

   Julien Rey

4. Step4.png

   06/Sep/2023 7:29 AM

   217 kB

   Julien Rey

5. Step5.png

   06/Sep/2023 7:29 AM

   280 kB

   Julien Rey

[JSWSERVER-21944] Old closed issues from a deleted Sprint get automatically added to a new Sprint

Mikołaj Pajor (Inactive) made changes - 07/Sep/2023 7:57 AM

Link

New: This issue duplicates JSWSERVER-21625 [ JSWSERVER-21625 ]

Mikołaj Pajor (Inactive) made changes - 07/Sep/2023 7:56 AM

Resolution		New: Duplicate [ 3 ]
Status	Original: Needs Triage [ 10030 ]	New: Closed [ 6 ]

Collapse comment: Mikołaj Pajor (Inactive) added a comment - 07/Sep/2023 7:56 AM

Mikołaj Pajor (Inactive) added a comment - 07/Sep/2023 7:56 AM

This bug is duplicate of another bug reported:
https://jira.atlassian.com/browse/JSWSERVER-21625

Expand comment: Mikołaj Pajor (Inactive) added a comment - 07/Sep/2023 7:56 AM

Mikołaj Pajor (Inactive) added a comment - 07/Sep/2023 7:56 AM This bug is duplicate of another bug reported: https://jira.atlassian.com/browse/JSWSERVER-21625

SET Analytics Bot made changes - 07/Sep/2023 4:03 AM

Support reference count

New: 2

Bugfix Automation Bot made changes - 06/Sep/2023 8:30 AM

Introduced in Version

New: 8

Julien Rey made changes - 06/Sep/2023 8:13 AM

Summary

Original: Old closed issues from a delete Sprint get automatically added to a new Sprint

New: Old closed issues from a deleted Sprint get automatically added to a new Sprint

Julien Rey made changes - 06/Sep/2023 8:12 AM

Summary

Original: Old closed issues get automatically added to a new Sprint

New: Old closed issues from a delete Sprint get automatically added to a new Sprint

Julien Rey made changes - 06/Sep/2023 7:36 AM

Description

Original: h3. Issue When a Sprint is deleted from a board, all the closed issues that belonged to that Sprint get automatically added to the next open Sprint that is on the board. h3. Environment Replicable on JSW (Jira Software) Server/Data Center on any version from 8.0.0. h3. Steps to replicate # Create a new JSW project and add a few issues to this project # Create a new board in this project and go to this board # Create 2 Sprints, for example #- A Sprint called "Sprint 19" #- A Sprint called "Sprint 20" # Add issues to both Sprints  !Step1.png|thumbnail! # Close 1 issue in the "Sprint 19"  !Step2.png|thumbnail! # Go back to the board and refresh the page. Notice that this issue is no longer showing in "Sprint 19" (Expected behavior, since closed issues from Sprints don't show in the Backlog view)  !Step3.png|thumbnail! # Delete "Sprint 19" via the menu *... -> Edit Sprint* # Start "Sprint 20" h3. Expected behavior The issue that was closed from the deleted Sprint should not be added to the new Sprint. h3. Actual behavior The issue that was closed from the deleted Sprint has been automatically added to the new Sprint.  !Step4.png|thumbnail! If we check the history of the closed issue, we can see 2 entries for the *Sprint* field: - one entry without any old and new value (which corresponds to the time the old Sprint was deleted) - one entry showing that the issue was added to the new Sprint (which corresponds to the time the new Sprint was started) SCREENSHOT h3. Workaround No known workaround.

New: h3. Issue When a Sprint is deleted from a board, all the closed issues that belonged to that Sprint get automatically added to the next open Sprint that is on the board. h3. Environment Replicable on JSW (Jira Software) Server/Data Center on any version from 8.0.0. h3. Steps to replicate # Create a new JSW project and add a few issues to this project # Create a new board in this project and go to this board # Create 2 Sprints, for example #- A Sprint called "Sprint 19" #- A Sprint called "Sprint 20" # Add issues to both Sprints  !Step1.png|thumbnail! # Close 1 issue in the "Sprint 19"  !Step2.png|thumbnail! # Go back to the board and refresh the page. Notice that this issue is no longer showing in "Sprint 19" (Expected behavior, since closed issues from Sprints don't show in the Backlog view)  !Step3.png|thumbnail! # Delete "Sprint 19" via the menu *... -> Edit Sprint* # Start "Sprint 20" h3. Expected behavior The issue that was closed from the deleted Sprint should not be added to the new Sprint. h3. Actual behavior The issue that was closed from the deleted Sprint has been automatically added to the new Sprint.  !Step4.png|thumbnail! If we check the history of the closed issue, we can see 2 entries for the *Sprint* field: - one entry without any old and new value (which corresponds to the time the old Sprint was deleted) - one entry showing that the issue was added to the new Sprint (which corresponds to the time the new Sprint was started)  !Step5.png|thumbnail! h3. Workaround No known workaround.

Julien Rey made changes - 06/Sep/2023 7:36 AM

Description

Original: h3. Issue When a Sprint is deleted from a board, all the closed issues that belonged to that Sprint get automatically added to the next open Sprint that is on the board. h3. Environment Replicable on JSW (Jira Software) Server/Data Center on any version from 8.0.0. h3. Steps to replicate # Create a new JSW project and add a few issues to this project # Create a new board in this project and go to this board # Create 2 Sprints, for example #- A Sprint called "Sprint 19" #- A Sprint called "Sprint 20" # Add issues to both Sprints  !Step1.png|thumbnail! # Close 1 issue in the "Sprint 19"  !Step2.png|thumbnail! # Go back to the board and refresh the page. Notice that this issue is no longer showing in "Sprint 19" (Expected behavior, since closed issues from Sprints don't show in the Backlog view)  !Step3.png|thumbnail! # Delete "Sprint 19" via the menu *... -> Edit Sprint* # Start "Sprint 20" h3. Expected behavior The issue that was closed from the deleted Sprint should not be added to the new Sprint. h3. Actual behavior The issue that was closed from the deleted Sprint has been automatically added to the new Sprint. SCREENSHOT If we check the history of the closed issue, we can see 2 entries for the *Sprint* field: - one entry without any old and new value (which corresponds to the time the old Sprint was deleted) - one entry showing that the issue was added to the new Sprint (which corresponds to the time the new Sprint was started) SCREENSHOT h3. Workaround No known workaround.

New: h3. Issue When a Sprint is deleted from a board, all the closed issues that belonged to that Sprint get automatically added to the next open Sprint that is on the board. h3. Environment Replicable on JSW (Jira Software) Server/Data Center on any version from 8.0.0. h3. Steps to replicate # Create a new JSW project and add a few issues to this project # Create a new board in this project and go to this board # Create 2 Sprints, for example #- A Sprint called "Sprint 19" #- A Sprint called "Sprint 20" # Add issues to both Sprints  !Step1.png|thumbnail! # Close 1 issue in the "Sprint 19"  !Step2.png|thumbnail! # Go back to the board and refresh the page. Notice that this issue is no longer showing in "Sprint 19" (Expected behavior, since closed issues from Sprints don't show in the Backlog view)  !Step3.png|thumbnail! # Delete "Sprint 19" via the menu *... -> Edit Sprint* # Start "Sprint 20" h3. Expected behavior The issue that was closed from the deleted Sprint should not be added to the new Sprint. h3. Actual behavior The issue that was closed from the deleted Sprint has been automatically added to the new Sprint.  !Step4.png|thumbnail! If we check the history of the closed issue, we can see 2 entries for the *Sprint* field: - one entry without any old and new value (which corresponds to the time the old Sprint was deleted) - one entry showing that the issue was added to the new Sprint (which corresponds to the time the new Sprint was started) SCREENSHOT h3. Workaround No known workaround.

Julien Rey made changes - 06/Sep/2023 7:36 AM

Description

Original: h3. Issue When a Sprint is deleted from a board, all the closed issues that belonged to that Sprint get automatically added to the next open Sprint that is on the board. h3. Environment Replicable on JSW (Jira Software) Server/Data Center on any version from 8.0.0. h3. Steps to replicate # Create a new JSW project and add a few issues to this project # Create a new board in this project and go to this board # Create 2 Sprints, for example #- A Sprint called "Sprint 19" #- A Sprint called "Sprint 20" # Add issues to both Sprints  !Step1.png|thumbnail! # Close 1 issue in the "Sprint 19"  !Step2.png|thumbnail! # Go back to the board and refresh the page. Notice that this issue is no longer showing in "Sprint 19" (Expected behavior, since closed issues from Sprints don't show in the Backlog view) SCREENSHOT # Delete "Sprint 19" via the menu *... -> Edit Sprint* # Start "Sprint 20" h3. Expected behavior The issue that was closed from the deleted Sprint should not be added to the new Sprint. h3. Actual behavior The issue that was closed from the deleted Sprint has been automatically added to the new Sprint. SCREENSHOT If we check the history of the closed issue, we can see 2 entries for the *Sprint* field: - one entry without any old and new value (which corresponds to the time the old Sprint was deleted) - one entry showing that the issue was added to the new Sprint (which corresponds to the time the new Sprint was started) SCREENSHOT h3. Workaround No known workaround.

New: h3. Issue When a Sprint is deleted from a board, all the closed issues that belonged to that Sprint get automatically added to the next open Sprint that is on the board. h3. Environment Replicable on JSW (Jira Software) Server/Data Center on any version from 8.0.0. h3. Steps to replicate # Create a new JSW project and add a few issues to this project # Create a new board in this project and go to this board # Create 2 Sprints, for example #- A Sprint called "Sprint 19" #- A Sprint called "Sprint 20" # Add issues to both Sprints  !Step1.png|thumbnail! # Close 1 issue in the "Sprint 19"  !Step2.png|thumbnail! # Go back to the board and refresh the page. Notice that this issue is no longer showing in "Sprint 19" (Expected behavior, since closed issues from Sprints don't show in the Backlog view)  !Step3.png|thumbnail! # Delete "Sprint 19" via the menu *... -> Edit Sprint* # Start "Sprint 20" h3. Expected behavior The issue that was closed from the deleted Sprint should not be added to the new Sprint. h3. Actual behavior The issue that was closed from the deleted Sprint has been automatically added to the new Sprint. SCREENSHOT If we check the history of the closed issue, we can see 2 entries for the *Sprint* field: - one entry without any old and new value (which corresponds to the time the old Sprint was deleted) - one entry showing that the issue was added to the new Sprint (which corresponds to the time the new Sprint was started) SCREENSHOT h3. Workaround No known workaround.

Load more older events