Redmine

I found a bug when adding relations and then deleting the parent.

Scenario:
Create issue A1 / A11 / A12 (issue A1 is the parent of A11 / A12)
Create issue B1

Issue A12 has a precedes relation to B1 (zero days)
If you delete A1 (and thus also a11/a12) issue B1 cannot be viewed or edited normally.
See error from the log below.

Please assist in solving this.

• redmine 0.8.3
• sqlite3 3.4.2
• ruby 1.8.6 (2007-09-24 patchlevel 111) [i486-linux]
• rails 2.1.2

NoMethodError (undefined method `start_date' for nil:NilClass):
/app/models/issue_relation.rb:72:in `successor_soonest_start'
/app/models/issue.rb:257:in `soonest_start'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.1.2/lib/active_record/associations/association_collection.rb:277:in `method_missing'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.1.2/lib/active_record/associations/association_proxy.rb:171:in `method_missing'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.1.2/lib/active_record/associations/association_proxy.rb:171:in `collect'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.1.2/lib/active_record/associations/association_proxy.rb:171:in `send'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.1.2/lib/active_record/associations/association_proxy.rb:171:in `method_missing'
/usr/lib/ruby/gems/1.8/gems/activerecord-2.1.2/lib/active_record/associations/association_collection.rb:277:in `method_missing'
/app/models/issue.rb:257:in `soonest_start'
/app/models/issue.rb:121:in `validate'

Hans Kazan wrote:

I found a bug when adding relations and then deleting the parent.

<...>

If you delete A1 (and thus also a11/a12) issue B1 cannot be viewed or edited normally.
See error from the log below.

This counts for every relation you make between issues, so also the other options in the "Related issues" section
of the issue.

Can anyone confirm this bug?

Hans Kazan wrote:

Hans Kazan wrote:
Can anyone confirm this bug?

Sorry for repeating my posts, editing would a nice feature...

I found the reason for the error message:
the table issue_relations is not updated (read: the relation is not removed when removing child issues).

After manually removing the corresponding record the issue can be viewed/edited as normal.

Any clue/hint when this can be solved or any directions were to look in order to temporary fix this?

Hans Kazan wrote:

Any clue/hint when this can be solved or any directions were to look in order to temporary fix this?

Change in lib/issue_relation_patch.rb

acts_as_nested_set

acts_as_nested_set :dependent => :destroy

Thanks for the quick reply, it works as expected.

And i would also thank you for this wonderful plugin!

I found that the closed sub-ticket is still listed in open issues.

btw, is it possbile to change the sub-ticket description in the add-sub-issue window?

Andrew Chaika, can you write some kind of manual for your plugin?
May be there is some important functions which I never being used because I knows nothing about it?

steeven lee wrote:

I found that the closed sub-ticket is still listed in open issues.

Subtickets are not filtered or sorted like main tickets

btw, is it possbile to change the sub-ticket description in the add-sub-issue window?

For now not, but this can be easily implemented.

Ilya Prokazov wrote:

Andrew Chaika, can you write some kind of manual for your plugin?
May be there is some important functions which I never being used because I knows nothing about it?

Ilya, all features of plugin are discribed in this thread. I will create wiki page with description when I had some time.

+1 for being able to add description when adding sub-issue.

Would it be a good idea to allow creating sub-issue from the right click menu of the issues itself rather than having to open the main issue details and then add the sub-issue.

Forgot to mention in last email - see the attached image in earlier post. Are the field names normal?

Using Redmin 0.8.4 with phusion passenger, ruby 1.8.7, rails 2.2.2

Ktool P wrote:

Forgot to mention in last email - see the attached image in earlier post. Are the field names normal?

Use patch provided by steeven lee in this topic (patch_lang_en_zh) to correct this

Change in lib/issue_relation_patch.rb

acts_as_nested_set

to

acts_as_nested_set :dependent => :destroy

I presume the "delete project" functionality works as expected in Redmine core,
so my first guess is that this could be related to this plugin, if not excuse me!

I detected a bug when deleting projects:
--> some issues from another project (with parent child issues also are removed.

Could it be that this change described above accidentally causes this unwanted side effect?

Any help is appreciated!

I can confirm that the this bug is related to the Grouping plugin.
It is reproducible even when archiving the project iso deleting.

When the project that is deleted contains no parent-child issues the deletion/archive action has no
side effects.

Please assist in a solution/work-around.

Hans Kazan wrote:

I can confirm that the this bug is related to the Grouping plugin.
It is reproducible even when archiving the project iso deleting.

When the project that is deleted contains no parent-child issues the deletion/archive action has no
side effects.

Please assist in a solution/work-around.

This is a feature, not a bug (c)
Solution/Workaround:
Change

acts_as_nested_set :dependent => :destroy

acts_as_nested_set

Maybe I was not completely clear in my explanation:

project x: contains issues with a parent-child relation
project y: no relations to project x, also contains stand-alone issues and parent child issues.

When you delete or archive project x, project y is affected (less issues, they are also deleted).

If we revert back the code, this situation would be solved I suppose but I get back the other issue mentioned in
this thread.

Thanks for your support.

The plugin combined with www.jsgantt.com is on the attached image. That is an early prototype for development testing. There is no promise on the date of availability.

Mykhaylo >>
What features have you planned in the Gannt plug-in? Maybe:
Change of start/end dates by dragging?
Move issue by Drag´n drop?

Or any other features. Damn I would like to see this in main trunk since our Redmine hoster does only provide straight vanilla Redmine functionality.

Lars,
The initial idea was to have a Gantt with arrows for relations between issues. Also I found grouping plugin to be very useful (e.g. for breakdown like planning) and wanted also to have that on a Gantt.
But it appeared to be more difficult to mix the jsgantt with Redmine mostly because of CSS issues and also unfortunately I cannot devote much time now to the development due to having no more interest from my customer in this.
Interactive mouse operations would be great here. This will bring Redmine closer to the desktop systems. But it will require significant time for implementing.

Lars Pehrsson wrote:

Mykhaylo >>
What features have you planned in the Gannt plug-in? Maybe:

• Change of start/end dates by dragging?
• Move issue by Drag´n drop?

See patch #2024 for a patch which provides such feature. Don't know what the current state of the patch is though.

HTH...

Andrew,

I tried to get the plugin from two computers. But both commands

git clone git://github.com/Ubik/redmine_issues_group.git

and

git clone http://github.com/Ubik/redmine_issues_group.git

fail with the same error:

warning: remote HEAD refers to nonexistent ref, unable to checkout.

I am fairly new to git. Searching for this error in the net tells me that this is a problem in the server-side repository and can only be fixed on the server-side repository. Maybe You can try a

git push --all

or try the solution posted on support.github.com

I'll try your ZIP posted in this thread in the mean-time. The screenshots are quite promising. Thanks for sharing this plugin!

try this

get the plugins revision

git clone git://github.com/Ubik/redmine_issues_group.git ./vendor/plugins/redmine_issues_group

show the remote repositories

git branch -r

get the remote branch and create local

git checkout -b my_local_redmine_issue_group origin:origin

Thanks Alexey, Your suggestion worked out for me (allthough I had to use origin/origin instead of origin:origin because git branch -r listed it as the only one). However, it would be nice if "remote HEAD referes to existent ref" ;-)

feature request for this plugin (if this is the right place)

it would be great if each group of issues had a 'select all issues in group' button

Markus Knittig wrote:

Erik Dannenberg wrote:

steps to reproduce: update the status or percentage of a ticket.
the status changes in the tickethistory are displayed twice for each status change.

I have the same problem...

I have the same problem too with this group issue plugin... on the production server.
when i copy the entire redmine dir and the database to my pc to test it, the problem is solved.
The only difference between the server and my pc is the version of Ruby ; 1.8.6 for the server, 1.8.7 for my pc.
So, what's happening when i edit and save an issue ?
The journal is created after saving the issue, but twice ???? Why ?