We have a deferred defect and future release is not defined. We also have deployable requirement created to track this deferred defect. In that scenario, can we mark the defect status as closed. So that we have only deployable requirement to track this deferred item.
At present my team is keeping defect Status as deferred. With this we do have two entities (one deferred defect and one deployable requirements) to track the same issue.
What is the best practice
@Srinivas Komaravolu welcome to the Atlassian community
It really has to do with you process. Usually having two or duplicate issues is not best practice. You should review the reasons behind having two issues and what the benefits to the team are, why it was done in the first place and what the downsides are. Then make a desicion as a team weather to have two issues or not.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.