Project

General

Profile

Activity

From 2014-10-03 to 2014-10-05

2014-10-05

22:29 Feature #559: Workflow Enhancements
Daniel Ritz wrote:
> A plugin for workflow enhancements in early stages. Currently only does a visualization with D3:
> ...
Just pushed an update that makes it possible to pre-define the issue statues for a tracker. Statuses defined in...
Daniel Ritz
21:13 Defect #8951: 404 w/ POST /issues.json (Filter chain halted as [:find_project] rendered_or_redirect)
Your log file shows that the JSON payload is not recognized/parsed by Rails. It can be due to malformed JSON data. Jean-Philippe Lang
16:59 Defect #8951: 404 w/ POST /issues.json (Filter chain halted as [:find_project] rendered_or_redirect)
Problem still exists in 2.5. Can reproduce with same output as Roman Lukmanov
Any updates on this?
Konstantin Manna
17:41 Feature #1517: Cumulative flow diagrams of trackers as some sort of project burn down graph
Steffen Gransow wrote:
> Any news on this? Is there a plugin that provides cumulative flow diagrams that track progress instead of time? Any burndown diagram plugins available that don't track just effort in terms of estimated/elapsed t...
Antonio De Marinis
15:20 Defect #17957 (Closed): Update of issue checklist delete and insert data again
Please, no plugin issue here in the Redmine issue tracker. You should contact the plugin author. Jean-Philippe Lang
15:19 Defect #17959 (Closed): Issue notes not previewed when project is changed
Fixed in r13428. Jean-Philippe Lang
14:12 Defect #17931 (Closed): note "Applied in changeset" generated multiple times for the same repo
This should be fixed by r13427. If a changeset from another repository that points to the same SCM backend (exact same URL configured in Redmine repositories) is already associated with the issue, other changesets won't be added. Jean-Philippe Lang
12:06 Feature #6118: Filter by parent task or subtasks
+1 Laurent Dairaine
00:34 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
Toshi MARUYAMA wrote:
> @ go2null wrote:
> ...
Ok, will do so next week.
@ go2null

2014-10-04

23:06 Defect #18032 (New): Continued numbered lists (#_) are not working as the textile syntax expects
# Item 1
Some text
#_ Item 2 (counting continued from the last Item, with the #_ marker)
Some text
#_ Item 3 (counting continued from the last Item, with the #_ marker)
Each item should be rendered as 1, 2, 3, but this is ...
Michel Behr
19:02 Defect #17904: group membership cannot be added to a project via REST API
I don't think this is a proper solution. this is a bug in the API design and it should not be masked by documenting it on the wiki. Alex Last
11:50 Defect #17904 (Closed): group membership cannot be added to a project via REST API
You just need to use the regular @user_id@ param to add a group membership, eg.
{"membership"=>{"user_id"=>275, "role_ids"=>[3]}, "project_id"=>"523"}
where 275 is your group id. I updated the doc: [[Rest_Memberships#POST]]
Jean-Philippe Lang
17:56 Feature #1091: Disabling default ticket fields per tracker
But the "priority" field still seems permanent. Is there a way to include that in the list of default fields that can be disabled? I have a specific tracker that doesn't need this field and it's causing some mild confusion with issue rep... Damon Tabb
15:42 Patch #17900: Allow change value of the time_entry object via controller_issues_edit_before_save hook from a plugin
I'm interested by the apply of this patch ! Bastien Sevajol
15:41 Defect #14428: ActionView::Template::Error (translation missing: en.number.human.storage_units.format)
Adi Kriegisch wrote:
> please reopen this issue: whatever client side setting shall never, ever cause a server error (500)!
Please contact plugin author.
Toshi MARUYAMA
14:06 Feature #18030 (New): Sorting and singnaling subtasks in Roadmap
I a ticket has subtasks: It would be very helpful if the subtasks are grouped relating to the main task. Even mor better: a small hint in css attribute about subtasks-depth. There is already a css class "child" in general.
+ Main Task...
Stefan Lindner
11:42 Defect #17928: Redmine Limitations (too many groups?)
If you have many groups, this problem may be fixed by r13149 (included in forthcoming 2.6.0), see #16905. Before the fix, all users from all groups were loaded when displaying the group list. Jean-Philippe Lang
11:38 Feature #17993 (Closed): Issues list : css tags to get sort orders
Added in r13425. You'll get 2 classes: one for the attribute (eg. @sort-by-created-on@) and one for the order (@sort-asc@ or @sort-desc@). Jean-Philippe Lang
09:51 Defect #18009 (Closed): model .rb file not matching model's class name in Alternativecustom_authentication_HowTo
Fixed, thanks. Jean-Philippe Lang
09:34 Defect #17944 (Closed): Helper hook doesn't change object attributes
Jean-Philippe Lang
09:33 Defect #17843 (Closed): Possible to delete issue even it is disabled in permissions
Jean-Philippe Lang
09:27 Feature #17955 (Closed): Add link to /time_entries/new from My Page Spent Time block
Added in r13423. Jean-Philippe Lang
09:25 Defect #17954 (Closed): /time_entries/new can't derive project from issue
Roger Hunwicks wrote:
> * the Project select list didn't have a default value
> ...
Fixed in r13422.
> * ideally, the Project select list shouldn't show Projects the user isn't a member of
The list shows projects for which the ...
Jean-Philippe Lang
03:29 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
@ go2null wrote:
> Toshi MARUYAMA wrote:
> ...
Did you modify gem *.rb files?
It causes unexpected result.
If you want to modify awesome_nested_set 2.1.6,
you should copy awesome_nested_set 2.1.6 as r12687 and r12688,
then remove a...
Toshi MARUYAMA

2014-10-03

20:03 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
So, based on #18018#note-12 above, it seems that two possible solutions are to
# include back the vanilla @awesome_nested_set 2.1.6@ and
## patch the @id@ to @name@, and
## no need for the @all.each { |p| p.set_or_update_position_unde...
@ go2null
19:16 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
deleted
@ go2null
19:07 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
Toshi MARUYAMA wrote:
> @ go2null wrote:
> ...
No, I just edited the one in @/usr/lib/...@ as I was trying different things.
@ go2null
19:06 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
OK, found why the problem happens.
Say I have a project with 4 subprojects (@[id] name@):
@=> [790] Project 1, [792] Project 2, [789] Project 3, [791] Project 4@
Here is the execution flow.
* @rebuild_tree!@
* @rebuild!(false)@
...
@ go2null
17:16 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
@ go2null wrote:
> I was referring to my manual patching of @.id@ to @.name@ in a pristine @awesome_nested_set-2.1.6@.
Did you *copy* @awesome_nested_set@ 2.1.6 to plugin/ directory?
Toshi MARUYAMA
16:57 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
Toshi MARUYAMA wrote:
> @ go2null wrote:
> ...
I was referring to my manual patching of @.id@ to @.name@ in a pristine @awesome_nested_set-2.1.6@.
@ go2null
02:24 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
@ go2null wrote:
> I tried both @rebuild!@ and @rebuild_tree!@, but without the patched @rebuild!@ in @awesome_nested_set@ it did not work.
What is patched?
@awesome_nested_set@ 2.1-stable on Redmine trunk is refactored heavily.
...
Toshi MARUYAMA
02:15 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
A naive question : is nested set functionality needed for Projects? @ go2null
01:44 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
I tried both @rebuild!@ and @rebuild_tree!@, but without the patched @rebuild!@ in @awesome_nested_set@ it did not work.
The issue is not with @rebuild_tree!@. In fact, based on some debug @puts@ that I added, the issue is actually th...
@ go2null
00:42 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
@ go2null wrote:
> Apparently, this is due to the removal, in v2.5, of the patched @awesome_nested_set@ plugin from the Redmine @lib/plugins@ directory.
> ...
It is because @awesome_nested_set@ after 2.1.6 refactoring is broken.
Toshi MARUYAMA
00:34 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
@ go2null wrote:
> *Workaround* (#6836#note-12) per "Ken Zalewski":/users/65030 still works.
> ...
It is not work because Redmine build tree @after_save@ .
source:tags/2.5.2/app/models/project.rb#L82
Toshi MARUYAMA
00:23 Defect #18018 (Needs feedback): Project Sorting by Name broken (for large project lists) in v2.x
Toshi MARUYAMA
00:20 Defect #18018: Project Sorting by Name broken (for large project lists) in v2.x
@ go2null wrote:
> Forgot to add, after the patch to @awesome_nested_set@, you need to run the following in the Rails Root directory.
> ...
You need to run @Project.rebuild_tree!@.
See source and comment.
source:tags/2.5.2/app/models...
Toshi MARUYAMA
16:10 Feature #18027 (New): Notification when deleting an issue
Currently, issue deleted are ... deleted :-)
To avoid to lost something, it would be great to have a final notification (same notifications rules + Redmine administrators). This notification should have the full history instead of final...
claude g
05:39 Feature #7360: Issue custom query: default query per instance, project and user
Florian Kaiser wrote:
> Maybe you can send a patch file to the redmine developers so they can add it easily.
Yes, i'll try.
Katsuya HIDAKA
 

Also available in: Atom