The saga of requirements changed after the feature is done continues:

Manager: “I have reopened your ticket cause it doesn’t fit the requirements”

*checks for requirements changes*

“Updated 2 mins ago”

You fucking piece of

Change it back, close the issue and tell them: "I've changed the requirements back, now they match 👍"

@bananaerror I love it 😂

Requirements should be in Git. Unchangeable, hashed. Of course you can patch them, but that will be a different set of requirements.

@homo-lorens if they were, management would not be able to blame devs for their (management) mistakes.

Fortunately the one deciding where to keep the specs is... oh... management

"Closed. Fixed inconsistencies in requirements."

Motherfuckers should just open a new ticket if they can't be bothered to do their job in time.

Companies praise Scrum and Agile and they don't know that both are based on "improvise along the way" that it is exactly what the OP is saying.

@jorgecastro No, you can improvise along the way while also admitting to the fact of improvisation by opening a new ticket if you want something else.

@homo-lorens

There is a subtle difference between:

* This could change

versus

* Our working model is done thinking that things will change.

@jorgecastro Adding on @homo-lorens’s comment:
Especially because companies tend to use metrix such as reopened tickets and development time in order to evaluate the dev, which means that while it is not an issue to change the software, it is fundamental to not generate blame out of nothing.

An update in content due to new design or new content should not be registered by the system as a poorly done job.
(I could add a ton on the stupidity of this metrix but...)

Aaaaaalso if we want to point fingers at what is or is not done by companies: I think I never witnessed a company releasing an MVP and improve it later.
Never.

If I where you I would do what @bananaerror said but also create a new ticket with the new requirements they the way it should be.

You could if you don't have the permissions ask the sysadmin (if you don't have permissions) to lock the description/definition field when the status is done.