part of story #21368 create mirrored iteration How to test: - Make sure your redis worker is running - Run `tuleap config-set feature_flag_program_management_display_iteration 1` to enable iterations. 1. If you have already made tests for this story, you can trigger a redis event for an existing PI with Iterations linked to it: - Enter the redis-cli in your redis container: $ docker exec -it tuleap_redis_1 redis-cli - Push a message to the events queue manually: > LPUSH 'app_user_events' '{"event_name":"tuleap.program_management.program_increment.update","payload":{"program_increment_id":6269,"user_id":110,"changeset_id":13408,"iterations":[{"id":6317,"changeset_id":13403},{"id":6318,"changeset_id":13404}]}}' Change the ids above according to your setup. You can get changeset_id in the Artifact View, there is a data-changeset-id attribute. 2. Otherwise, if you don't have pre-wired artifacts: - Edit a Program Increment artifact and add one or more artifact links with _is_child type to Iteration artifacts. 3. With either method 1. or 2., a log message will be added to "program_management_syslog" for each iteration: [debug] Team name: <first team name> The log message only exists for testing purposes, to show that we retrieve teams. It will be removed on next commits. Change-Id: Ia307e357afd919c2c3b7b1ba552c2b219e3631ad

+285 −16

Author

Joris MASSON (jmasson) 2021-10-01 12:05

Committer

Joris MASSON (jmasson) 2021-10-04 13:56

Hash d56a3767bd56416fda8e989d0c7d7068e12f51c7

Parent 19f9f1bfd4c252f78816d3e7558b848e0ad8f769

Reference git #tuleap/stable/d56a3767bd56416fda8e989d0c7d7068e12f51c7