jamieshepherd / tygr

Repository for the Tygr issue management system, by

Tygr - Issue management system

####Version 1.0.11

This repository hosts the source code for the tygr issue management system, a project and issue management system developed primarily for companies in the elearning industry. The project is open source under the MIT license.

Production prerequisites

• PHP 5.5

Development prerequisites

• Composer
• Node.js
• Laravel Homestead*

*Homestead is not required, but makes development and deployment very easy.

Installation

To begin developing Tygr, you must first have the aforementioned pre-requisites. You can use the following commands to install your development environment.

• Run homestead up to start your local development environment, if using Homestead
• Run composer update to get all of the PHP dependencies
• Run npm install to get any Node dependencies
• Run gulp watch to process SCSS
• Connect to your local VM homestead ssh(if using Homestead) and cd to your project directory
• Run php artisan migrate --seed to migrate and seed the database

License

This repository is released as open-sourced software licensed under the MIT license

tygr's Issues

Show user rank on users page

Show what rank a user has on the following page:
http://tygr.jamie.sh/users

E.g.

• Super Admin
• Staff
• Admin

Good to have if fault finding or seeing why someone cant do something

Employee "Projects" button in navigation

This could be confusing, and might be worth removing for employees. Instead, if they wanted to view Sponge projects they can do so the same way they would a clients. Speak with Al about this before implementation.

Bug when Changing a client from Pitch to Client

Assuming we win the pitch, this is something that presumably needs to happen?
Currently error messages come up:
http://puu.sh/fnwkv/c18dd0a69a.png

Address 404 for some uploads

Likely need to strip out some entities from uploaded file names, for example the file "1ii1ii-ss%2B%282015-02-03%2Bat%2B12.37.11%29.png" could not be found.

layout/general

At 1024x768 the projects resize slightly oddly and there are some overlaps with buttons over content. Not a big deal, but just fyi:
http://puu.sh/fnoyf/4a2b9c8b37.png

Issue creation assigning

If a Sponge employee creates an issue, they might want to automatically assign that to a client. Perhaps have a radio button on creation which by default is selected to Sponge, but can also select the client.

Redesign client projects list

It's not the most effective design right now, it could be made a lot warmer and with more useful information.

PUT requests

Look into replacing some POST with PUT requests.

404 errors for non authed users

If they can't auth, they should still get HTTP respones.

Create another issue

Louise mentioned that she'd like to be able to input multiple issues, rather than being sent straight to the issue you just created. This makes sense as there could be many issues wanting to be created at one time, and would require less effort. Will likely just send user back to the create form upon submission.

Improve the dashboard

Lots of things to happen to the dashboard, some interesting statistics, personalised to the user.

Ability to hide navigation bar

Sometimes users will just want to work off a list of issues, so the ability to hide the navigation bar will be useful.

Realistic seed list

For the beta, create a realistic seed list with real users. Also remove all of the test data (such as fake clients, issues, etc.)

Show user assigned groups

Not sure if we should also show the users assigned groups on the following page too:

http://tygr.jamie.sh/users

Groups get assigned from the following url:
http://tygr.jamie.sh/users/create

Issue History comments

On the ‘Issue History’ section of the Issue Details page, are all comments viewable to all users?
For example where dev/design add comments to issues, are these then viewable to the client? If so, would it be worth considering something along the lines of a private or internal comment feature?

Select rank and client for user

Make it better than entering an integer into a text box. Radio buttons for rank, dropdown for client perhaps.

Dropdown menus for Project creation

To simplify and reduce potential for typo issues, you could have dropdown menus for Authoring Tool and LMS specification.
Also it might be worth having the type of disribution- i.e. iPads, Desktop etc and an area for short notes that can show up on the project page for everyone to see- i.e. 'This will be translated into Greek and Russian' or whatever.

Issue history client tag

The client tag after the users name when they leave a comment currently only says "Sponge UK", should say client name if they are a client.

On delete cascade

On delete of clients, remove projects, on delete of projects, remove issues, on delete of issues, remove issue history. Cascade delete all.

Make design responsive

Not high priority, but would be nice to have a completely responsive design.

The word "issue"

The verdict is out on this one, some people like issue, some people see it as too negative. Other suggestions have been 'amendment', 'change', 'ticket'. Create a poll and get opinions! Try to get this in before a first version release.

Reports

Similar to the dashboard, Louise thought it might be a good idea to generate reports at the end of projects to see where time was spent. Lots of data driven metrics that we can use for future projects. Look into some nice solutions for this, but probably push this to a post-release change.

Check validation screens for edit

node/edit screens still need to be checked for @endif errors

Redesign the table a little

With new features coming in and out, it will be worth redefining the basic table style to make it a little cleaner. Look at Github issues (this thing) for some inspiration, as they handle it rather elegantly.

Provide feedback on login

Provide feedback for login. Incorrect password etc.

Remove assigned to me button

As we now have a filter issues box (which includes assigned to me), this button has become a bit redundant. Clear up some space and remove. (Confirm with Alan).

Force unique email

Force unique email with FormRequest validation.

Crashes

When logged in as jamie.shep********* from the following page:

http://tygr.jamie.sh/projects/blueindustries/firesafety

I click the "You can click here to take a look at these issues."

The following URL crashes and shows error messages:
http://tygr.jamie.sh/projects/blueindustries/firesafety/issues/filter/me

Claiming an issue

Ben had the idea that employees could claim issue (invisible to clients) where if an employee is working on an issue, it gives the impression to others that it's already been "claimed" by them. Just a deeper level of assigning an issue. Will look into possible solutions for this to try and make 1.0.0 - but might be further into future.

If form request fails, fill out form with details again

They might type something for ages, but then form request fails, so they lose all their data.

The Resolve feature

Would it be worth considering functionality for two, or even three stage resolution. For example, if the developer working on the issue marks the issue as resolved, this will then need to be QA’d and then marked as resolved. Once with the client, they will need a way to signal their sign off. While this could be done with comments, it would be simpler in viewing terms to simply review the list of issues and their resolved/active status.

'Log an issue' page

Would be good that the client has to give the URL for the resource they're working on prehaps have this as a required field this way we don't have issues of 'well it looks fixed on my screen' only for them to be using vesion 0.14 of the spanish translation when we're looking at French v5....

Be particularly useful for things like JIBS where we have multiple versions of essentially the same project

Unit tests

Write some unit tests, why weren't these done before you lazy sod!

Issues locked on client side once submitted

Once an issue is entered by the client they can still edit it- this could cause confusion and potentially mean things are missed. Should the client be able to resolve issues that aren't assigned to them? Obviously they need to check stuff off on client review, but surely then the PM will assign the issue to them to close off?

Email alerts

Is there any way to set email notifications on projects or issues? This would definitely be needed, to know when to check on client feedback or when issues are resolved or assigned back.

Ensure certain ranks can only see specific levels

Make sure only certain ranks have certain access to certain permissions! Rank 1 can create edit delete users, rank 2 can view them, rank 3 can do neither for example.

Unique project names for clients

Make sure projects must have unique project names (and stubs) per client. Add this functionality into validation form requests.

Merge official L5 release

Laravel 5 has officially been released, so merge the latest version!

Login background image

Get design to create or look at possible background image for login page. There's a high chance MD won't like the unsplash one!

Branding

Do client side pages need to be branded to the client colours, as in review area?
Additionally, logos etc.

Blob storage

Speak with Chris about deploying images, attachments, to blob storage on Azure.

Rename label for new user

Rename to "Full name"

Nicer error pages

Currently, the error pages are incredibly basic for HTTP responses (404,403,500 etc.) - look at improving these so it's not so alarming to hit a dead link.

Make adding attachments easier

I'd like to introduce something like simple drag anywhere and drop file uploads for issues. Must be extremely lightweight whatever the solution, preferably not jquery.

Assign users to groups

Need the ability to assign users to groups, if they're from Sponge UK, we have to be able to specify the subgroups they are part of. Same for editing.

Consolidate pages?

Is there anything more that needs to go on the project overview page? If not, could the issues be listed on that page, rather than having to click through again to them? This might make the interface a bit slicker as you'd have all the project details on one page.

View all at once or detailed view

The project managers have highlighted the wish to be able to see all of the issues at once in a singular view, possibly to be printed to pdf for example. This will allow them to go through and time all of the issues, so will need to look into an elegant solution. One option will just be to have a "print all" button which sends everything to a text-only printable format.

Make changing version more obvious, ability to move issues across versions

At the moment the way to change a module version is literally editing the project and changing the version name implicitly. Would be nice to have a 'New version' button, and also the ability to move issues from one version to another.

Add route arguments after FormRequest

For example public function update(Request $request, $id)

Batch assign function for Issues

Some sort of higher level check box to select and assign many issues to depts/people so PMs don't have to open every issue and assign.

Thanks Bye