Control the process of Product Owners changing story content

[David Milligan]

What is the best way to control Product Owners enhancing a story once it is in production. 

Stories are being changed and amended but without anyone bringing it to the attention of dev management. Need a process where changes are proactively flagged so the impact can be reviewed and assessed.

[Ryan Fish · Accepted solution]

Sounds like the PO and developer team need to talk more often to become more transparent  :)
You can create a JQL query and subscription:
project = <project name> and updatedDate >= -<3h>
where updatedDate can be h hours, d day, w weeks

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

One of the ways to do this would be to prevent edits to the story after it goes past a certain state in the workflow (like Resolved or Ready for Prod or something similar).

You can do this using workflow properties. And you can even restrict the permission to a certain group after a stage in the workflow.

That is a way of locking down the tool. You might also want to consider controlling it via process - by educating the product owners, discussing the changes in retrospective sessions, actively watching JIRA tickets and so on.

[David Milligan]

That's good thank you.

I had thought that perhaps locking the story down to a group, after a point in the workflow, would be the way forward, and monitoring any changes thereafter.

Then creating new stories for any additional agreed functionality.

Thanks Dave

[Ryan Fish]

@David Milligan
You could also set the security level so only you, admins or specific roles can see them. When you want the issues to re-appear remove the security level .

If you are happy with the options, please close the issue :)