Paul Eggleton 560628c0e5 rrs: duplicate releases from first plan when adding a new plan ... It's a pain to have to add all the releases when adding a new maintenance plan. Since these are likely to be the same (or similar) for every plan, then duplicate them across from the first plan when you save a new one. Also add "default" milestones on the assumption that other layers probably won't want to use the 4-milestone split per release, but there do have to be some milestone records, so just create one milestone for each release. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>		2018-05-04 23:57:53 +12:00
..
migrations	rrs: releases should be unique by plan and name, not just name	2018-05-04 23:57:53 +12:00
static	rrs/base_toplevel.html: Navbar redesign	2018-05-04 23:57:52 +12:00
tools	rrs_upgrade_history: improve checkout logic	2018-05-04 23:57:53 +12:00
__init__.py	rrs: show full name in admin	2018-05-04 23:57:52 +12:00
admin.py	rrs: duplicate releases from first plan when adding a new plan	2018-05-04 23:57:53 +12:00
apps.py	rrs: show full name in admin	2018-05-04 23:57:52 +12:00
context_processors.py	rrs: Add application	2018-05-04 23:57:51 +12:00
models.py	rrs: releases should be unique by plan and name, not just name	2018-05-04 23:57:53 +12:00
urls.py	rrs: add charts page	2018-05-04 23:57:53 +12:00
views.py	rrs: add charts page	2018-05-04 23:57:53 +12:00
wsgi.py	rrs: Add wsgi file for serve with gunicorn	2018-05-04 23:57:52 +12:00