Manage Jenkins views as code/yaml in JJB (2.1) allows projects to define and manage there own views. Also managing Jenkins views through code is better choice since stale views need not be cleaned up, if they are no longer required.  
*This saves time and resources by allowing projects to define and manage their own views.

[1.] https://github.com/opendaylight/releng-builder/blob/master/jjb/releng-views.yaml

[2.] https://github.com/opendaylight/releng-builder/blob/master/jjb/yangtools/yangtools.yaml#L100-L104

 
For the benefit of the others in the team, can refer to the changes below for ODL which uses view templates:

https://git.opendaylight.org/gerrit/#/c/77599/