Discarded Jira Stories Rationale

[Tommy Le]

Is it possible for Jira Stories that get discarded to prompt a rationale? We complete monthly reviews that are automatically exported to an excel document where we have to check individually each Jira Story has a comment on why the story was discarded. This could be code that is no longer used or simply an out of date story that is no longer valid. But this is a really manual process and was wondering if there were any way to make this automated or a simple check.

[Trudy Claspill · Accepted solution]

Hello @Tommy Le 

Welcome to the Atlassian community.

What do you mean by "discarded"? Are issues being changed to a specific status that represents "discarded"?

And what type of project(s) does this concern? Get that information from the View All Projects page under the Projects menu.

If a status change is involved and this concerns Company Managed projects, then you could use a Transition screen and a Validator in the workflow transition to require users to input information when executing that transition. You could even have a custom field specifically for recording that information.

If this concerns Team Managed projects those do not yet support Transition screens. But you might still use a validator/rule during the transition to confirm that the custom field has been filled with a reason before the transition is attempted.

[Tommy Le]

First thank you for your response. Issues do get changed to a discarded status. These are in fact company managed projects, but with that information it definitely helps. I'll bring these up and see if that would be within policies to implement.

[Varsha Joshi · Accepted solution]

Hi @Tommy Le 

It absolutely can be done in the workflow. You need to edit your workflow validators to enforce the rational before closing it. You would need admin access to make changes to your workflow for the story Issue type. 

-Varsha

[Tommy Le]

Incredible thank you!