Teams, Buckets, Issues

I'm archiving this repository as GitHub Projects do almost everything this project set out to do.

I Got Issues provides a few simple building blocks for organization and then gets out of the way so you can do your work.

Core Concepts

I Got Issues is team specific and repository agnostic so you can import issues from any number of repositories into your team's buckets.

I Got Issues improves the signal to noise ratio for your team by not showing every issue in every repository that you work in. Import issues that need your team's attention and ignore everything else.

I Got Issues does not force a specific workflow but it was developed with a particular workflow in mind.

Our Workflow

Buckets

My team at work prioritizes our issues into three buckets, In Progress, Up Next, and Icebox.

Prioritization Meeting

Approximately once a week we have a meeting where we work together to prioritize what is up next. Everyone on the team has ownership in the process and decisions made.

Importing

We only import issues that we need to talk about and possibly work on.

Working An Issue

When I start working on an issue I move it from Up Next to In Progress and assign it to myself.

Completing An Issue

I can close the issue by simply checking the box once I have completed the work.

Shipping

At our next prioritization meeting we discuss and then ship the completed issues which are automatically rolled up into a Markdown ship list that we can post somewhere for the rest of the company to see.

Auditing

Finally we can audit the history of decisions we made.

Prerequisites

• postgres or whatever database you want to use (update database.yml accordingly)

I install postgres using homebrew:

brew install postgres

And then I start the postgres server with:

postgres -D /usr/local/var/postgres

Setup

Clone the repo.

git clone https://github.com/jonmagic/i-got-issues.git
cd i-got-issues
bundle

Now go to https://github.com/settings/applications and register a new application. You'll need the Client ID and Client Secret, if you run the server locally the Authorization callback URL is http://localhost:3000/auth/github/callback.

Create a .env file in the root of the project and enter the following details filling in with the values you just copied after registering a new application:

GITHUB_KEY=client_id_from_the_app_you_just_registered
GITHUB_SECRET=client_secret_from_the_app_you_just_registered

Now setup the database and start the server.

rake db:setup
rails server

Open your browser to http://localhost:3000 and choose a team :) Enjoy!

Development

Run the tests with rake.

Deploying

I setup the app on Heroku in a matter of minutes. You shouldn't have any problems.

1. Create the Heroku app and add the remote to your local git repository
2. Register app on GitHub https://github.com/settings/applications
3. Set the two environment variables GITHUB_KEY and GITHUB_SECRET using heroku config:add
4. Deploy the app to Heroku with git push heroku
5. Run database migrations with heroku run rake db:migrate

Fire it up in your browser and see if it worked.

Contributing

Read the guide to contributing.

Contributors

• @jonmagic
• @juliamae
• *jankeesvw
• @muan

License

See LICENSE.