How can we alter the Sprint flow to retain Sub-Tasks with "In Progress" (Closed) Status?

[Mandy Froelich]

Hello, 

First - thanks for your patience as I try to explain our ask. 

Our Salesforce development team has requested the ability, when working through the sprint process, for "Pending Release" items that need additional time to QA before officially being "Completed" to NOT be carried into the next active sprint. 

In other words, the objective is, within a sprint, to be able to mark things as closed (as "Pending Release") that still have not been packaged/published. 

1. Does this ask make sense? 

2. Is there a way to do this? 

To better explain, below is the ORIGINAL issue our team was assigned.

The process below did not enable the Development team to retain "Pending Release" issues. Instead, they were pushed into the next sprint because they were not completed. 

***

We are trying to improve our release management process (packaging process) using Jira. For every issue type that is Documentation, we need a new status called "Pending Release" so that we have "Draft," "Pending Release," and "Closed" as the THREE statuses as the documentations (Sub-tasks). Once someone has finished writing the documentation and it has gone through the editing process, it gets set to "Pending Release" status. When packaging occurs, we also go through all of the Documentations in "Pending Release" status, PUBLISH them, and mark those Documentation Trackers as "Closed". 

Then, for another project (ASD) board itself, we want to move the status "Pending Release" to the "Closed" column and move everything in the "Pending Release" status to "Closed" with a status of "Pending Release."

In the future, when something is defined as DONE by development, we’ll move it to "Closed" in the "Pending Release" status. 

If possible, when someone transitions something into the "Closed" Column, it can only be set for STORIES and BUGs to "Pending Release" or "Cancelled." "Closed" would be off the board but would not show up in the "Closed" column. 

Then, when we truly close a sprint, everything remains in that "Closed" column and the Sprint pointing/burndown statistic will represent accurately. Then, when we do want to package, you will have to run reports on Bugs, Issues, and Documentations find the ones in “Pending Release”, move those into your Publishing Processes for Software and Documentation and then change the status to "Closed." 

Once again, the objective is, within a sprint, to be able to mark things as closed that still have not been packaged/published.