community-platform
community-platform copied to clipboard
IA Pages - automatically update dev_milestone
Description :
Based on other fields values (perl_module, production_state, blockgroup, deployment_state, and the current dev_milestone) we should be able to automatically update the dev_milestone field for any IA.
This PR also introduces a new dev_milestone value: "offline".
How the dev_milestone will be determined:
- online, live, blockgroup, perl_module, deployment_state = live
- online, live, no perl_module/blockgroup/deployment_state = offline
- offline, planning/development, no blockgroup, no deployment_state = no change (still planning or development)
- offline, deprecated = no change
- offline, complete, no deployment_state = complete
- offline, planning/development, blockgroup = testing
- offline, live, blockgroup, deployment_state = offline
- offline, complete, blockgroup, deployment_state = no change
To do:
- [ ] Make sure all the possible cases are taken into account.
- [ ] SQL to automatically update existing IAs.
- [ ] Tweak the ghIssues.pl script to use the new statuscheck function when automatically updating the dev_milestone
- [ ] Back end tests
Reviewer notes :
References issues / PRs:
Who should be informed of this change?
Does this change have significant privacy, security, performance or deployment implications?
Checklist :
- [ ] Back end tests (perl, scripts)
- [ ] Front end tests (js, integration)
- Browser verification
- [ ] IE
- [ ] Chrome
- [ ] Firefox
- [ ] Safari
- [ ] Opera
- Mobile verification
- [ ] iOS
- [ ] Android
online, live, no perl_module/blockgroup/deployment_state = offline
Probably should be something other than "offline" since it indicates an inconsistent state.
In general I don't think we are determining dev_milestone here. Yes, we've used that column in the past for status but
- It can be edited
- It probably can and should be modifiable independently of the status, e.g. we could set it to dev when making an enhancement even though still online.