Part of story #12189 prevent field modification according to state How to test: Add the feature flag: - In forgeconfig table, add a row with name = sys_should_use_read_only_post_actions and value = 1 Forge your DB: - Get a transition id and insert a new row in plugin_tracker_workflow_transition_postactions_read_only - Get the id you just inserted, get field ids and insert new rows in plugin_tracker_workflow_transition_postactions_read_only_fields When you do a GET /tracker_workflow_transitions/{id}/actions with your transition id, you should see the new post actions in the returned json. When you delete a transition that has this new post action, the rows in DB should be deleted. When you delete a workflow (by changing its field in the UI), the new post action rows in DB should be deleted. Will be done later: - REST test. Can't do them without XML import or PUT post action Change-Id: I6ad1788de4d2d058621d45c6ce88d8e01e8b57c9

+517 −54

Author

Joris MASSON (jmasson) 2019-03-04 17:21

Committer

Joris MASSON (jmasson) 2019-03-07 11:10

Hash dd69c25c49d1420bf481a7cec0d14a9d028a8727

Parent 43146658c6849b583410eff9523b5c36a8257695

Reference git #tuleap/stable/dd69c25c49d1420bf481a7cec0d14a9d028a8727