puppetserver 1.2.0 2016-09-08 Release (SERVER-1522)

[SERVER-1537] Close all resolved tickets in Jira Created: 2016/08/29  Updated: 2016/10/14  Resolved: 2016/09/08

Status: Closed
Project: Puppet Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Sub-task Priority: Normal
Reporter: Jeremy Barlow Assignee: Jeremy Barlow
Resolution: Done Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Team: Systems Engineering
Sub-team: emerald
Sprint: Server Emerald 2016-09-07, SE 2016-09-21, SE 2016-10-05

 Description   

Close any tickets that have been resolved for the release.

https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20SERVER%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%22SERVER%201.2.0%22%20AND%20status%20%3D%20Resolved

There is a bulk edit at the top (a gear with the word "Tools"). Should you decide to take this route:

  • Select Bulk Change - All # issues
  • Step 1 - choose all relevant issues (likely all of them)
  • Step 2 - Select "Transition Issues"
  • Step 3 - Select "Closed"
  • Step 4 - Select "Fixed" in Change Resolution.
  • View what is about to change and confirm it. Then commit the change.

Dependencies:

  • Packages pushed


 Comments   
Comment by Jeremy Barlow [ 2016/09/08 ]

Closed all issues for the release, so closing this issue.

Comment by Steve Barlow [ 2016/09/27 ]

Accidentally set tickets in active sprint to closed. Moving back to resolved.

Generated at Wed Nov 13 16:56:10 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.