mikelbring / tinyissue Goto Github PK

I've been having an issue with assigning new users to projects.

Create a new project and while still on the projects/new page, try and assign a user. It won't function properly, i.e it will try and make the AJAX call but fails because it returns 0 users.

If you click create, it creates the project just fine. Now delete the assigned user (you, the one who just created the project) and try and assign new users to the project. Again, it won't work because the function returns 0 users.

I was looking through the code pretty quickly and came across the project model - the users_not_in() function which calls the users() function within the same class. This function will always return an empty array as long as the projects_users table in the database is not populated with some form of data.

If you delete all the assigned users of a project, and look at your console, you will see what the GET request is trying to query:

SQL: SELECT * FROM `users` WHERE `id` NOT IN () AND `deleted` = ?

The NOT IN () part is the problem as it needs to be passed something.

I am currently trying to figure out the best way to handle this, but I think an open discussion would be great. @mikelbring

When adding a comment to an issue, the date & time of the comment is always the same as the date & time of when the issue was created.

The screenshot shows an issue created 7th December and two comments created 13th December.

I pasted in a body containing this:

I'm not entirely sure what went wrong, but in any case any time I try to view this issue, it redirected me to a broken URL. Basically the proper URL with the issue number chopped off and replaced by http:%3A something blah blah. It didn't actually do a meta refresh, and it didn't encode the entire URL into my new broken URL, it just threw some garbage on the end.

Fortunately I patched it up without much trouble using phpmyadmin, just changing the < and > to & entities and now it's happy. But TinyIssue's renderer should probably treat this more intelligently; it took me a while to figure out how to fix this, or even why it was broken.

Install program can check if pdo, db drivers, mcrypt is installed and available prior to installation.

All of the pages that are doing some kind of count function are throwing errors.
SQL: SELECT COUNT(*) AS [aggregate] FROM [projects_issues_comments] WHERE [issue_id] = ? ORDER BY [created_at] ASC
The problem appears to be because it's trying to order results for the count: is invalid in the ORDER BY clause

The pages that are throwing the errors are /project/##/issues, /project/##/assigned, and /user/issues.

I'll take a look!

Message :
Directive 'magic_quotes_gpc' is deprecated in PHP 5.3 and greater

It would be great to have a public project specific issue reporting page, where anyone can enter an issue.

I'm able to get the first config setup screen. But after clicking "Run Install", it goes blank. The error log says,

[16-Aug-2012 14:28:44] PHP Parse error:  syntax error, unexpected T_STRING in /home3/som_dir/public_html/tinyissue/app/laravel/hash.php on line 1

Any help? Where im going wrong?

The Global Application Statistics on the Administration page are incorrect. Archived Projects, Open Issues, and Closed Issues all show 0; Tiny Issue Version shows v1.1.0; and Version Release Date shows 2-20-2012. The first two items--Total Users and Active Projects--are correct. (Actually, I guess, in my case zero archived projects is correct, but the others are definitely wrong.

It would be great if the login page would redirect you to the page you attempted to view while logged out.

Ex. I try to go to http:///tinyissue/index.php/project/10, and get redirected to the login page because I haven't logged in in a while. After logging in it'll redirect me back to http:///tinyissue/index.php/project/10 instead of the dashboard.

Have y'all considered switching to using a SQLite database? It would make Tiny Issue pretty much platform-agnostic, and really easy to run in a Windows environment.

Just installed tinyissue and missed 2 very useful features: 1. export issue list to some pdf/xls/ods. 2. An optional field "Estimated time left" for the issue which could also rename itself to "Time spent" when issue is closed (or make 2 fields). And sum of all times below.
I think both features would be very useful for making periodic reports for your boss and/or client :)

I gave this a brief test drive this morning, and I like it. But with how my company would use it for users to report bugs, the last we want to have happen is for the user to do anything but report/comment on bugs. For them to assign someone to the task should be beyond their permissions.

There are two open issues. Neither are assigned to me. When I select Administration in the nav bar, the Open Issues count is 0.

I think I have tracked it down to the project/issue model in the count_issues function, line 209, where the query is being executed. First, I don't know why you have a "group by" clause as you only want the total count. I think the group by will only show the count from the first project.

But even when I remove the group by, the query is not returning any results to the $count var. The check !$count always returns false and as a result the count is zero.

Can't see how to fix this yet, as I'm just getting started.

As more users and projects are added to tiny issue, search becomes important for ease of use. a full text search is preferable

This one's new with 1.2.1 (as far as I've noticed). When I click "Close Issue," the confirmation dialog has no text in it. It still works if I click OK.

I found your software really attractive, thank you for sharing with us!

I'd like to use this software in our little company, but i need italian
language to give it to my collegues.

any plan to add language support?
i saw language directory in the repository, but is somekind limited.

of course, for translation phase i can help for italian support...
my english is terrible but i can assure my italian is far better :-)

Regards,
Matteo

This is a most important feature to track dependent issues. This helps prioritize issues and add more value to the issue tracker

I get the follow install issue after it creates the config.app.php file.

"Parse error: syntax error, unexpected T_STRING in ../app/laravel/laravel.php on line 1"

Any reason why this would be happening?

I think it would be a good idea to separate public files (index.php and assets) from the source files. With the directory structure right now, you are able to access the app folder.

Maybe something like that (image from tutsplus.com):

First of all, thanks for making this laravel application as open source.

And to enhance, just a thought. How about adding one more user group "Clients".

An admin can create a project and send invite to a client user and given access to that project. The client user can create issues for his project and assign it to Manager or some group. Then the issue can be tracked as per the existing flow.

Primary goal of this idea is to have a client specific login where the clients can create and talk about issues. ( A basic idea from basecamp or MavenLink etc.,).

Reason why I'm suggesting this idea is like the basic group "User" is capable of creating multiple projects (where this will not be the case for a client. Admin creates a project and invites clients).

Any suggestions?

Thanks,

• goG

Hi, I have trouble running tinyissue on my server. Debian wheezy, php 5.4.4, apache 2.2.22, mysql 5.5.28

The installer went fine, but when trying to access my tinyissue/ directory from a web browser i get this error message:

Unhandled Exception
Message:

require(): Cannot redeclare class laravel\bundle

Location:

/var/www/tinyissue/app/laravel/autoloader.php on line 134

Stack Trace:

#0 /var/www/tinyissue/app/laravel/laravel.php(42): Laravel\Error::shutdown()
#1 [internal function]: Laravel\{closure}()
#2 {main}

Apache error log:

Wed Dec 19 22:28:44 2012] [error] [client 192.168.1.254] PHP Fatal error:  require(): Cannot redeclare class laravel\\bundle in /var/www/tinyissue/app/laravel/autoloader.php on line 134

Any clue on why this is happening? thanks

Rather than pointing to something like app/assets/js/app.js Laravel seems to be creating links like http://tinyissue.loc/project/app/assets/js/app.js which includes an extra "project" folder in front of the path. On other pages it looks like http://tinyissue.loc/index.php/administration/app/assets/js/app.js.

In other words, it always appends the current URL path to the location when Asset::styles() is called. I assume this is just a Laravel 1.0 bug.

I'm using Nginx and so it might not like the $_SERVER['REQUEST_URI'] that nginx provides or something.

When the responsibility for a task changes, it would be nice to be see this happening inline with the comments on the task.

Typically our task workflow in Lighthouse is Create a Task > Add Comment > Assign it a Developer > Add Comment > Assign it to a Tester > Close

Request to add LDAP authentication feature. This will be one more application for users to remember a username and a password. Instead, LDAP will bring easier adoption of the fine application which administrators will love to use.

The automatic link creation is great, but what about switching to straight-up markdown? I bring this up because of Issue #51.

I'll start working on it. I don't think it'll be too hard. But I thought I'd open the issue up for comment.

See:

http://al.robotfuzz.com/~al/random/tiny.png

Using relesae v1.2.3

Hi,
I see that you started to translate system with strings stored in tables but with the same structure as gettext. But is it now easiest to use POT files for contributors ?

We you put in project name non ascii chars they saves as question mark.

It seems there is a problem with table structure

instead of

CREATE TABLE IF NOT EXISTS projects (
...
name varchar(255) character set latin1 default NULL,

should be

CREATE TABLE IF NOT EXISTS projects (
...
name varchar(255) character set UTF8 default NULL,

@mikelbring we'd chatted a while ago about building a marketing / promo site. Worth creating a separate repo for this so we can get the ball rolling? Could just be regular vanilla HTML for now?

I've been working on porting Tiny Issue to work in an IIS+MSSQL (https://github.com/ddreier/tinyissue-iis) and everything has been going swimmingly. But there seems to be a few custom MySQL queries scattered throughout the models, and those kind of throw a kink in the works.

I'm going to work on getting rid of them, but it would be great if no more were created

Thanks!

It seems there is an issue with creating a new issue. ^_^

When you attempt to create a new issue you receive the error message:

Unhandled Exception

Message:

Call to undefined function Laravel\mcrypt_create_iv()
Location:

C:\wamp\www\tinyissue\app\laravel\crypter.php on line 43
Stack Trace:
#0 [internal function]: Laravel{closure}()
#1 {main}

Everything else seems to be working fine.

Is it possible to create a documents area where users could upload some files by project ?
When you are in the project, you have the following menu :

• Activity
• Open Issues
• Closed Issues
• Issue Assigned To You
• HERE you could have "Documents"

And when you click on the link, you could have the list of all documents uploaded for the project and a form to upload others files with an option to create folders.

This is probably beyond the scope of a bug patch that mikelbring would normally do, but I have a question/request about this project.

How possible would it be to implement a "mode" essentially where users don't have to be registered to post issues or comment on them? They would take the role of "User".

I understand that you probably won't have the resources or time to add this yourself, but can the way the code is structured allow for it, and where would you start poking around to add this?

Thanks!

Currently, URL's are displayed as text. Making them links automatically and opening them in a new window will add usability.

Hi,
i have problem after upload, i see the thumbnail but nothing when i try to open them

We took a wrong turn.
Server Error: 404 (Not Found)

What does this mean?

We couldn't find the page you requested on our servers. We're really sorry about that. It's our fault, not yours. We'll work hard to get this page back online as soon as possible.

Perhaps you would like to go to our home page?

well i change right to 777.

but now when upload another problem

If image have space in name, then the full image won't display after. it's a bug

Hi,
I can't get through the Install because I get this error:

PHP Fatal error:  Cannot re-assign auto-global variable _POST in /var/www/install/install.php on line 33

I google this and this might be a problem through change from PHP 5.3 to PHP 5.4

On my computer, the text "Tiny Issue" is visible behind the image "Tiny Issue", on the top left of the home page.

Tiny Issue Account type : administrator
Operating System : Microsoft Windows 7
Screen Resolution : 1440 x 900
Web Browser : Chrome 22.0.1229.79
Browser Size : 1440 x 772
Color Depth : 32
Javascript : Yes
Flash Version : 11.3.31
Cookies : Yes
User Agent : Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.4 (KHTML, like Gecko)

I get the follow error when trying to add a new project: (I'm using the Development branch on php5.4)

Unhandled Exception

Message:

SQLSTATE[42S22]: Column not found: 1054 Unknown column 'updated_at' in 'field list'

SQL: INSERT INTO projects_users (user_id, project_id, role_id, updated_at, created_at) VALUES (?, ?, ?, ?, ?)

Bindings: array (
0 => '1',
1 => 1,
2 => 0,
3 => '2012-04-04 09:43:51',
4 => '2012-04-04 09:43:51',
)
Location:

../app/laravel/database/connection.php on line 228

I had an issue assigned to me, and tried to set it back to "no one" (to effectively mark it as inactive). Now whenever I try to view the project that contains that issue, I get this:

Unhandled Exception

Message:

Trying to get property of non-object
Location:

/var/www/default/issues/app/application/views/activity/reassign-issue.php on line 8
Stack Trace:
#0 /var/www/default/issues/app/laravel/laravel.php(36): Laravel\Error::native(8, 'Trying to get p...', '/var/www/defaul...', 8)
#1 /var/www/default/issues/app/application/views/activity/reassign-issue.php(8): Laravel{closure}(8, 'Trying to get p...', '/var/www/defaul...', 8, Array)
#2 /var/www/default/issues/app/laravel/view.php(325): include('/var/www/defaul...')
#3 /var/www/default/issues/app/laravel/view.php(306): Laravel\View->get()
#4 /var/www/default/issues/app/laravel/view.php(500): Laravel\View->render()
#5 /var/www/default/issues/app/application/views/project/index/activity.php(11): Laravel\View->__toString()
#6 /var/www/default/issues/app/laravel/view.php(325): include('/var/www/defaul...')
#7 /var/www/default/issues/app/laravel/view.php(306): Laravel\View->get()
#8 /var/www/default/issues/app/laravel/view.php(357): Laravel\View->render()
#9 /var/www/default/issues/app/laravel/view.php(316): Laravel\View->data()
#10 /var/www/default/issues/app/laravel/view.php(306): Laravel\View->get()
#11 /var/www/default/issues/app/laravel/view.php(357): Laravel\View->render()
#12 /var/www/default/issues/app/laravel/view.php(316): Laravel\View->data()
#13 /var/www/default/issues/app/laravel/view.php(306): Laravel\View->get()
#14 /var/www/default/issues/app/laravel/view.php(500): Laravel\View->render()
#15 /var/www/default/issues/app/laravel/response.php(234): Laravel\View->__toString()
#16 /var/www/default/issues/app/laravel/response.php(220): Laravel\Response->render()
#17 /var/www/default/issues/app/laravel/routing/controller.php(276): Laravel\Response::prepare(Object(Laravel\View))
#18 /var/www/default/issues/app/laravel/routing/controller.php(155): Laravel\Routing\Controller->execute('index', Array)
#19 /var/www/default/issues/app/laravel/routing/route.php(140): Laravel\Routing\Controller::call('project@index', Array)
#20 /var/www/default/issues/app/laravel/routing/route.php(111): Laravel\Routing\Route->response()
#21 /var/www/default/issues/app/laravel/laravel.php(193): Laravel\Routing\Route->call()
#22 /var/www/default/issues/index.php(34): require('/var/www/defaul...')
#23 {main}

Since tiny issue uses PDO, adding PostgreSQL support should not be too involved. This provides flexibility for installations running postgresql and also easier to add when the project is young.

I would like to have an option to receive email notification when an issue, assigned to me or one that I have "Subscribed" to, changes.

There is an error on line 65 in the development branch. Had to add a comma to line 64 - see below.

• Encryption support, SSL/TLS, used with gmail servers *
  Default: blank
  */

'encryption' => ' '
'username' => ' ',
'password' => ' ',
),

changed to

• Encryption support, SSL/TLS, used with gmail servers
• Default: blank
  */

'encryption' => '',
'username' => '',
'password' => '',

),

The count of the number of issues assigned to you does not return a correct number. The problem can be found in the model project.php in the count_assigned_issues function.

Using Laravel's fluent Query Builder, I changed the code to look like this:

[code]
public function count_assigned_issues($user_id = null)
{
if(is_null($user_id))
{
$user_id = \Auth::user()->id;
}

/*
$sql = '
SELECT COUNT(id) AS total
FROM projects_issues
WHERE project_id = ? AND assigned_to = ? AND status = 1
';

    $result = \DB::first($sql, array($this->id, $user_id));

    return !$result ? 0 : $result->total;

*/
return = \DB::table('projects_issues')
->where_project_id($this->id)
->where_assigned_to($user_id)
->where_status(1)
->count();
}
[/code]

Now it works.

Tiny Issue auto-detects URLs in Issues and comments and that is awesome! But it also includes single periods in URLs if they are at the end of a sentence. Ex: http://d.pr/i/qSKy

I just noticed that for "url.com." the period isn't included. But for "url.com/test." the period is.

the error show when i add a new user,i have install the hmailserver on my server,what can i do?
how can i make it work? can some one help me,thanks a lot!

error info:

Unhandled Exception

Message:

mail() [function.mail]: SMTP server response: 550 The address is not valid.
Location:

D:\www\tinyissue\app\vendor\Swift\lib\classes\Swift\Transport\SimpleMailInvoker.php on line 49
Stack Trace:
#0 D:\www\tinyissue\app\laravel\laravel.php(36): Laravel\Error::native(2, 'mail() [You have bee...', 'Message-ID: <13...', '-fsupport@honst...')
#3 D:\www\tinyissue\app\vendor\Swift\lib\classes\Swift\Transport\MailTransport.php(176): Swift_Transport_SimpleMailInvoker->mail('denis.lei@sunbo...', 'Your Tiny Issue...', '

You have bee...', 'Message-ID: <13...', '-fsupport@honst...')
#4 D:\www\tinyissue\app\vendor\Swift\lib\classes\Swift\Mailer.php(86): Swift_Transport_MailTransport->send(Object(Swift_Message), Array)
#5 D:\www\tinyissue\app\application\libraries\mail.php(63): Swift_Mailer->send(Object(Swift_Message))
#6 D:\www\tinyissue\app\application\models\user.php(309): Mail::send_email(Object(Laravel\View), 'denis.lei@sunbo...', 'Your Tiny Issue...')
#7 D:\www\tinyissue\app\application\controllers\administration\users.php(26): User::add_user(Array)
#8 [internal function]: Administration_Users_Controller->post_add()
#9 D:\www\tinyissue\app\laravel\routing\controller.php(313): call_user_func_array(Array, Array)
#10 D:\www\tinyissue\app\laravel\routing\controller.php(273): Laravel\Routing\Controller->response('add', Array)
#11 D:\www\tinyissue\app\laravel\routing\controller.php(155): Laravel\Routing\Controller->execute('add', Array)
#12 D:\www\tinyissue\app\laravel\routing\route.php(140): Laravel\Routing\Controller::call('administration....', Array)
#13 D:\www\tinyissue\app\laravel\routing\route.php(111): Laravel\Routing\Route->response()
#14 D:\www\tinyissue\app\laravel\laravel.php(193): Laravel\Routing\Route->call()
#15 D:\www\tinyissue\index.php(14): require('D:\www\tinyissu...')
#16 {main}

I would like three additional fields to each issue;
Category - Bug, Enhancement,New Feature, Data Issue, Specification, Tracking, etc...
Status - Open, Closed, Testing, Hold, Cancel, etc...
Priority - Critical, High, Medium, Low

It would be real nice if these could be added, modified, deleted by the admin.

How can I help implement these?

Application looks very nice, but I miss labels and status for issues. Any future plans for this ?

I had a crazy whim that it might be easy to convert the installer to use Laravel's Fluent queries. Well, I got all of the queries created and all of the requires added so that the only error I'm getting is "No direct script access."

Any suggestions?