The tool is currently used to show progress against linked goals and how those goals are represented within teams, and groups.

Install homebrew if not on your machine.

brew install postgres
git clone http://github.com/peterkappus/panoflex.git
cd panoflex
cp sample.env.txt .env
bundle
#issues compiling SSL support for puma? Try this:
gem install puma -v '2.12.1' -- --with-opt-include=/usr/local/opt/openssl/include
#Make sure Postgres is running now... (see below)
bundle exec rake db:setup

This app uses Google Auth to authenticate users and create new accounts. Each time a user logs in his or her name and email address are used to create a new account in the system.

NOTE: The first user to log into the system will automatically be made into an admin. It is impossible to make yourself into a non-admin.

• Visit the Google developer console
• Create a new project (Name it whatever you like)
• Click "Credentials" (on the left-hand nav)
• Click on "OAuth consent screen"
• Create & save a new product
• Click "Create Credentials"
• Select "Web application"
• Provide a name (whatever you like)
• Add your local callback URI (e.g. http://localhost:5000/auth/google_oauth2/callback) to the Authorised Redirect URIs section
• Add the callback URL for production (e.g. http://app.herokuapp.com/auth/callback)
• Click Save (TWICE)
• Copy our Client ID and Secret to your .env file

It also has a Procfile which you probably won't need to touch.

Start postgres. If you used Brew, you can run brew install postgres to get info on how to manually start it. Usually it looks something like this: pg_ctl -D /usr/local/var/postgres start

Or, to have it run constantly in the background, brew services start postgresql

To start the server use $ heroku local

• Set up a heroku account (or use an existing one)
• Create a new app
• Decide if you want to point it at your own fork of the app, a particular release, or branch, or the HEAD. For production instances, it's recommended you point it to the latest stable release.
• Go to the "Settings" tab
• click "reveal config vars"
• Create new keys for GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and any other config params set in your .env file

TIP: Need to backup your heroku database before deploying?

$ heroku pg:backups capture --app APPNAME

Want daily backups? heroku pg:backups schedule DATABASE_URL --at '02:00 Europe/London' --app APPNAME

You can save it locally if you want:

$ curl -o latest.dump `heroku pg:backups public-url --app APPNAME`

Read more about postgres backups including how to restore.

This app attempts to use BDD principles as much as possible. It still needs proper unit tests but in the meantime, all new functionality should be covered by integration tests. To make cucumber run for this app, here's what I have to do (after installing all the gems, etc).

$ bundle exec cucumber

Or only run @wip (work in progress) tests:

$ bundle exec cucumber:wip

• Cascading assignment (a check box? or easy way to assign all sub-goals to the same owner/team/group as the parent goal when editing)
• Email notifications: notify a goal owner when a sub-goal gets updated
• Comment on a goal (& email the owner)
• Comment on a progress update (& email the update maker)
• Comment on a comment and update all the previous commenters and the owner
• Tree view
• "Nudge" a goal (emails the owner)
• "Like" an update (emails the owner)
• Disallow entering a deadline before the start_date (use validates_date gem?)
• Version control to see when/why/how/and by whom a goal change was made.
• Ability to view old versions of goals
• Add a RAG status based on % complete vs time remaining
• Rename "deadline" to "end_date" everywhere
• Browse goals by due-date quarter (how will this affect scoring?)
• Add unit tests using Factory Girl & Rspec
• Start using the GOV.UK components instead of reinventing the wheel
• Ween ourselves off of bootstrap and just use the standard GOV.UK CSS.

• Ability to download all status updates
• View all progress updates for a goal
• Add name of person who created score in export (and email)
• Allow an arbitrary number of levels for export (export contains all goals)
• Search for goals using free text
• Search based on person name
• Ability to create teams & groups
• Ability to delete teams & groups (only when no goals are assigned)
• Pretty doughnut graphs (via Google charts) showing distribution of delivery status within a group/team/person/SDP/etc
• Click a name and see all goals owned by that person
• Capture monthly (or weekly?) local backups
• Ability to show only SDP goals
• Hide scores & scoring functionality (make scores optional)
• When reporting, add requirement to select a status:, Not Started (default), On-track, Off-track, Significant Delay/Issue, Delivered- Implement new "box-based" UI (see Lucy F's mockup)
• Add ability to report progress at all levels.
• Add ability to flag a goal as belonging to the SDP (+ tests)
• Assign "owners" to goals who can update progress.
• Allow cabinetoffice.gov.uk email addresses to login
• Don't allow people to assign goals to a team and group which don't match (e.g. don't select GOV.UK and Data)
• Change goal edit form to disallow assigning a time if goal has sub-goals. Explain that team assignment will be determined by sub-goal teams.
• Ability for Administrators to promote/revoke admin status for existing users.
• Exporting goals now includes all updates/scores.
• Hide date fields when editing a goal with sub-goals (and explain why)
• Sort sub-goals by start date
• redirect to parent goal when successfully creating sub-goal (based on user research)
• 25% performance improvement by saving derived scores in Goal model (BEFORE: Expand_all w/ 406 goals took ~ 14seconds to load & render AFTER: 10.46seconds
• Links are blue again so it's obvious you can click 'em
• Refactor sub_goals and clean up "expand all" rendering using rows & columns
• Determine start/end dates by looking at sub-goals
• Created a simple /dashboard resource to show some useful stats...
• Add user to goals and scores so you can see who created/last-modified a goal or score.
• Add start/end dates to goals (and include in form)
• Add links for admins to edit team/group info
• Setup Cucumber and Capybara and write some basic tests
• use "slugged" names for team/group URLs (e.g. groups/operations vs groups/4)
• show teams for parent goals where all children have the same team
• Make an "about" page explaining the thing and that its a pre-alpha proof of concept
• Fix the header so the proposition links don't disappear on mobile
• Add Group & Team goals pages & links
• Add GOV.UK page layout template
• Paginate full role listing
• Associate roles to functions (initially by function_name) w/ error reporting

• Clickable hashtags in goal text?
• Make names click-able to search for all roles using that person
• Search for role by type
• Add non-people costs (EPIC)
• Filter to show vacant roles per team (by month)