Using Will not Implement for Sub-tasks

[Jeff Murray]

Hello -

In some cases, when we create subtasks they will not be used once we get into the development. So we have used the status will not implement or cannot implement. However, with these status we cannot complete the story. We don't want to delete due to reporting needs.

Thank you.

[Valerie Knapp]

Hi @Jeff Murray , thanks for your question.

It sounds from your description that the Story isn't getting closed because the Subtasks have a status in the done category but they don't have a resolution.

Please check the workflow for the Subtask. When they are transitioned to the status of 'will not implement' or 'cannot implement', you will need to add a post function to set the resolution as closed (or something to say you have stopped working on the issue). In this way, the Story 'understands' that the work on the Subtasks is concluded, and can also be closed.

I hope this helps but if you need further assistance, please don't hesitate to ask.

Cheers

[Jeff Murray]

Hello Valerie -

Can you explain further (the steps) to add a post function to set the resolution as closed. 

Thanks,

Jeff

[Valerie Knapp]

Hi @Jeff Murray , thanks for your message.

If you go into the Jira system settings, Issue menu and find the workflow for the issue type, you will need to edit it to get a view like this 

Here, I have clicked on the arrow next to the Done transition and you can see this box pops up on the right. This is where you can set any kind of automations for the transition to the status of Done. In this case, we are not interested in limiting who can view and execute this transition (Conditions), or checking for something to be added or updated during the transition (Validators), we want to do something after the transition has taken place. We want to update the resolution post transition, for which we need a post function.

If you click on Post Functions, you will see a list of actions that happen after the  transition. If the Resolution wasn't already being set, you would click on, 'Add post function'

and then the next screens take you through the steps to find the field you want to update

and here you choose the Resolution, hit add, and then publish the workflow

You can tell this has worked when you transition a Subtask to a done status and there is a resolution here next to the status -

I hope this helps you but if you need further assistance, please just let us know.

Cheers

[Jeff Murray]

Thanks, Valerie! I'll give it a try a bit later and respond back.

Jeff

[Jeff Murray]

Hi Valerie -

Finally getting back around to this. Per your instructions, in step one, we don't have the choice for post functions. The only item in done when clicking into it is properties. Am I able to add post functions?

Thanks......

[Valerie Knapp]

Hi @Jeff Murray , thanks for your message.

You are saying in this screen -

that you only see Properties, and not any of the other options?

Please can you check / confirm if this a team-managed or a company-managed project? I just learned that this configuration is not possible in a team-managed project - 

Solved: Cannot add a post function to a jira web workflow (atlassian.com)

Please give me your feedback and either I or someone else will try to help.

Cheers

[Jeff Murray]

Hi Valerie -

Background:

 Issue: At the sub-task level, when we use the status “Will Not Implement”, the story will not close when we select the “Done” status. Forces us to use the status of “Done” to be able to close the story.

I created this Atlassian post for resolution. I was provided responses provided for the resolution. I followed her recommendations / steps in the post and added a post function. It did not resolve the issue. We have noticed the below issue and are trying to determine if the recommendation caused the problem. 

Per the screenshots below, the status is showing “testing” when these issues were removed from the sprint. However, in the second screenshot, for these issues' status’ we had selected “Will Not Implement”. Is this issue derived from the change I made initially? 

[Jeff Murray]

Hello Atlassian support -

Requesting a response as time allows, thanks!

Regards,

Jeff

[Riley Venable]

If the subtask is in a status that is not mapped to a column, it will not be considered in the Scrum backlog and will not be included in the reporting. However, if the subtask is in a mapped status, but cannot be completed, it may still be visible in the backlog and reporting. It is recommended to discuss with the team and determine the best course of action for handling these types of subtasks.