Part of story #12189 prevent field modification according to state How to test: Build (or import) a tracker with all fields. You should test: - string - text (HTML format or Text) - artifact link - computed (manual and autocomputed) - date - file - selectbox - radio button - multi selectbox - checkbox - open list float, int and permissions on artifact are bugged [0] For each of those fields, forge your DB: - Get a transition id (for example, from "To Do" to "On going") 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 Now, create an artifact for this tracker and set its "status" (or whatever field defines the workflow) to "On going" (same as the "to" for your transition above). Once the artifact is "On going", when you try to edit the read-only fields defined above, the backend should stop you with a feedback "Fields are not valid" [O]: Known issues: - If you configure a float, int or permissions on artifact field as read-only in the workflow, you won't be able to update the artifact anymore. Those fields do not identify changes correctly, even when you don't change the value they will be marked as changed. Change-Id: I693779f8cda33da7eeb6422bacd20e53b9503723

+723 −53

Author

Martin GOYOT (goyotm) 2019-03-15 17:33

Committer

Joris MASSON (jmasson) 2019-03-19 13:57

Hash 750ed2f8d71cb296876075fa246979c55ad99940

Parent 636982b74daf8bf7c688f91dfbe9d8e1b2d2271d

Reference git #tuleap/stable/750ed2f8d71cb296876075fa246979c55ad99940