Do you to keep a PBI's current status visible?

As PBIs evolve, it's common for their initial descriptions to become outdated or for significant developments to occur that must be recorded for the benefit of the entire team.

Whenever a PBI necessitates an update, the team should add a comment to the issue, detailing the change or event.

bad example lots of non descriptive comments — Figure: Bad example - Lots of non-descriptive comments cluttering the issue.

good example adding context via comment — Figure: Good example - Extra context added via comment.

In cases where an update is long standing or important, it should be appended to the bottom of the issue description. This update must include the date it was made, serving as a chronological record of changes. In addition, a comment should be left on the issue thread to inform team members that significant information has been added to the issue.

Re-assigning the PBI? You don't need to comment or change the PBI description. GitHub and Azure DevOps both track this via the "Assignees" field and audit changes.