Inspiration
As a CUNY student any issue I had always ended up with me being bounced from department to department with no resolution in sight. This was the basis of the ticketing system we created, called Bounceless, which is meant to make these processes more efficient.
What it does
It allows students to create issues and push those to relevant departments. Members of that department then have the ability to comment on the issue, transfer it, or attempt to resolve it. This is then recorded in an open and transparent chronology.
All of this is overseen by administrators, who have exclusive rights to reassign individual users role permissions and also have the ability to comment on or resolve issues.
Javascript is used to make the site more dynamic.
How we built it
The majority of the code is in Ruby, erb, HTML, and Javascript. The database is currently in SQLite. We also built an API that could be used to extend the application to iOS
Challenges we ran into
Time was tight, wifi was scarce. Our database relations were complex and required a lot of revision before we had it mapped out exactly as we needed.
Accomplishments that we're proud of
Complex database relations and joins necessary to give all users their due access (and no more). Nested routes for students and faculty, keeping permissions separate. Implemented administrative structure (including admins and faculty members) for better security.
What we learned
We learned about Adobe cloud services. Also how to interface a Rails API with Swift.
What's next for Bounceless
Build out our API backend, make the frontend more dynamic by further integrating AJAX calls and javascript handling of data. Ideally we would make it into a Single-Page Application. Then, maybe expand full functionality to iOS devices.
Improve CSS and layout generally.
Log in or sign up for Devpost to join the conversation.