Activity
From 2013-02-15 to 2013-02-17
2013-02-17
-
22:50 Feature #13088: CDN support to jquery/ui lib
- Sure, you can do pretty much everything in @additional_environment.rb@ if you know about Rails configuration (which changes quite often BTW), Ruby, regexp and all but that's not what we can call "configuration". What I see here is a way ...
-
19:47 Feature #13088: CDN support to jquery/ui lib
- Jean-Philippe Lang wrote:
> JQuery and JQuery-UI are merged in Redmine assets so it wouldn't work.
That was a non-functionnal example for demonstration purpose.
> ...
It's Rails configuration?
> and would make the upgrade proce... -
11:26 Feature #13088: CDN support to jquery/ui lib
- JQuery and JQuery-UI are merged in Redmine assets so it wouldn't work. It's hacky anyway and would make the upgrade process painfull. That's the purpose of this request to make using a CDN straightforward.
-
22:27 Defect #13197: Don't send password in plain text via email after registration
- AFAIK, it's only when an admin changes a user's password that it can be sent by email. Could you give the steps to reproduce your issue?
-
20:10 Defect #13197 (Closed): Don't send password in plain text via email after registration
- When the registration process is set to manual account activation, the new user gets automatically an email with his (self set) username and password in plain text.
This is a dangerous security risk!
And it is not necessary. The us... -
19:42 Defect #13195 (Closed): Delete wiki page Sandbox
-
18:34 Defect #13195 (Closed): Delete wiki page Sandbox
- Please delete [[Sandbox]], I used it for testing and can't delete it myself.
-
18:43 Feature #13194: I'm lost
- I agree that all these gems, bundler, rake, ... can be confusing for people not familiar with rails, but what exactly can be improved in [[RedmineUpgrade]]?
I have the same gut feeling as you, that documentation can be improved. I just ... -
14:18 Feature #13194: I'm lost
- Merci, Jean-Philippe, you've nailed it. I upgraded that plugin (a custom one developed for our forum by a friend), and now everything is progressing.
For reference, the history of every step I ended up taking, and a full log of the st... -
13:50 Feature #13194: I'm lost
- > You specified: shoulda (> 3.3.2) and shoulda (> 2.11)".
Redmine depends on shoulda 3.3.2 but it looks like you have an extra dependency on this gem. Do you have any plugin with a Gemfile (eg. @/plugins/*/Gemfile@)? -
13:42 Feature #13194 (Closed): I'm lost
- Dear Redmine developers, please hear me out...
I'm a long-time user and supporter of Redmine. Over the years, I've tracked lots of releases (started at 1.02, IIRC). Am now at 2.2.2. The system I maintain is being used by over a hundre... -
18:22 Patch #12645: Russian numeric translation
-
14:27 Defect #12243: Ordering forum replies by last reply date is broken
- Thank you! Confirmed to work perfectly now - http://jeelabs.net/projects/cafe/boards/6
-
12:12 Defect #12243 (Resolved): Ordering forum replies by last reply date is broken
- The updated_on column is no longer updated when adding a reply hence the sort was broken. It's now fixed in r11424. Thanks for pointing this out.
-
11:20 Defect #12243: Ordering forum replies by last reply date is broken
- Ping? Sorry for making a nuisance of myself, but could someone please reply and explain or address this issue?
-
13:03 Feature #13183 (Closed): add wiki format to custom issue fields (text areas) optionally
- Same as #1179.
-
12:44 Patch #11898: Inheritable issue categories
- I finally found some time for Redmine (sorry but holidays and Valentine's day were most important to me :-) .
In my first patch a view used a helper function declared in an other view's helper. It worked fine in previous versions (of ra... -
10:37 Feature #11014: Advanced projects dependencies support
- > I would like to be able to see all issues fixed in AppA-1.0 and AppB-2.4
If you wanna see all issues being fixed in several versions of any project you need a filter for project versions on all projects issues. I thought that is alrea... -
09:14 Feature #13147: worflow enhancement: overleap status if allowed
- Either b1 or b2 or both has to be set. Sure that only possible with JS and ajax validation.
-
00:05 Feature #13147: worflow enhancement: overleap status if allowed
- Say role 1 is allowed to do a->b1 and a->b2, role 2 is allowed to do b1->c and b2->c, status b1 has a required field f1 and b2 has a required field f2. A user with role 1 + 2 would be allowed to do a->c. What happens with f1 and f2?
-
02:20 Feature #824: Add "closed_on" issue field (storing time of last closing) & add it as a column and filter on the issue list.
- For roadmap/changelog: extending subject to better circumscribe the new feature.
-
02:04 Feature #4730 (Closed): Add Closed Date to Issue Filter
- "Closed" (@closed_on@) field that stores the time of the last closing, while preserving the value when reopening an issue, is added in r11402. It has been made available as a column and filter on the issue list in r11403. Both were done ...
2013-02-16
-
22:39 Patch #12645 (Closed): Russian numeric translation
- Mikhail Velkin wrote:
> and divide the option "notice_failed_to_save_time_entries" to several separate bloks.
I create new issue #13192.
-
22:38 Defect #13192 (Closed): Russian "notice_failed_to_save_time_entries" translation
- #12645#note-5
-
22:37 Feature #13147: worflow enhancement: overleap status if allowed
- I don't mean to skip the status but instead of sending the form twice is is possible to do sveral steps in one. Tne conditions of alle steps merge together and you have the sum of all steps packed into one chnage of the form. It is alrea...
-
22:11 Feature #13147: worflow enhancement: overleap status if allowed
- Terence Mill wrote:
> No, your are wrong. Its already possible, but cumbersome.
No, I'm not wrong. Doing a->b->c is not just doing a->c with more clicks. If no role is allowed to skip the status b in the workflow, I don't think that ... -
21:43 Feature #13147: worflow enhancement: overleap status if allowed
- No, your are wrong. Its already possible, but cumbersome.
You have todo more clicks and results in more (useless) form change events (aka more history). Of course moving from a->c must respect all required fields, what mean if from a-> ... -
16:42 Feature #13147: worflow enhancement: overleap status if allowed
- I understand your problem. But we would end up in a situation where someone with role 1 and role 2 could do things that neither role 1 nor role 2 can do. It could be misleading and not desirable.
-
22:35 Patch #13190 (Closed): Bulgarian translation (r11404)
- Committed in trunk r11407, thanks.
-
13:10 Patch #13190 (Closed): Bulgarian translation (r11404)
- Translated:
* field_closed_on
Chanched:
* field_subject -
18:29 Defect #13189: Redmine version in trunk should be based on next major release
- Ah, I see. Yeah, sending a warning seems to be a better solution. Shall I put a patch together?
-
10:56 Defect #13189: Redmine version in trunk should be based on next major release
- OTOH, if we set trunk version to 2.3.0 just after 2.2.0 is released, the IssueQuery model might not be present yet in a 2.3.0 trunk. So I don't know if there's a right solution. Maybe we could change the behaviour of requirements when us...
-
00:51 Defect #13189 (New): Redmine version in trunk should be based on next major release
- I'm developing a plugin against trunk, which relies on the IssueQuery class. This class only exists in trunk. Therefore the first version which will contain IssueQuery will be 2.3.0, so it makes sense to put this in my init.rb:
-
17:26 Defect #13185 (Resolved): Redmine claims RMagick is not available
- My problem was already described in http://www.redmine.org/boards/2/topics/2699 and #10724. So it doesn't seems to be a redmine bug. However, until now I couldn't solve it. If I have more time I will try to figure out the problem.
-
15:22 Feature #13191 (Resolved): Custom query: When an issue was applied to version x?
- Ok, I'm using now the column "version". For the last days that's sufficient.
-
15:02 Feature #13191 (Resolved): Custom query: When an issue was applied to version x?
- On the roadmap page I can't recognize which issues were added in the last days. I'd like to have a possibility to sort/query the date when a issue was applied to the version x.
Now I see 68 issues for redmine 2.3 and I never know whic... -
12:36 Defect #13188 (Closed): Forms are not updated after changing the status field without "Add issues" permission
- This is fixed in r11405, thanks for pointing this out.
-
11:02 Defect #13188: Forms are not updated after changing the status field without "Add issues" permission
- This was broken long time ago by r4011.
-
10:59 Defect #13188 (Confirmed): Forms are not updated after changing the status field without "Add issues" permission
-
11:38 Defect #13184 (Closed): 500 internal server error when changing tracker
- Duplicate with #11005.
-
10:42 Feature #824 (Closed): Add "closed_on" issue field (storing time of last closing) & add it as a column and filter on the issue list.
- Feature added.
Filou Centrinov wrote:
> Always show the date of last closed status. If never has been closed before, don't show any date.
This is how it was implemented as most people requested this behaviour. The closed_on colu... -
09:23 Feature #7312 (Closed): Email language
- Duplicate with #8147.
-
09:20 Feature #12413: Support per-language email footer/header
- Toshi MARUYAMA wrote:
> Duplicate with #5990.
not #5990, it is #8147.
-
09:16 Feature #12413 (Closed): Support per-language email footer/header
- Duplicate with #5990.
-
08:13 Defect #13036: auto generated comment "Applied in changeset xxx" is not link to commit
- Dietmar Hofer wrote:
> I guess the extended syntax is intentional, because now more then 1 repository per project are allowed. With svn repos, that means the repo must be included in the commit macro in order to uniquely identify the co... -
08:10 Defect #13036: auto generated comment "Applied in changeset xxx" is not link to commit
- Dietmar Hofer wrote:
> seems to be a duplicate of #13005
No. #13005 is abount repoid "contains underscores" -
00:50 Defect #12243: Ordering forum replies by last reply date is broken
- Any news on this? I can't seem to find any logic to how forum posts are ordered when clicking on the "Last message" header.
-
00:47 Feature #11014: Advanced projects dependencies support
- +1
I have the same needs. -
00:46 Defect #13104: Wrong year in redmine footer: move redmine into 2013
- Florian, Daniel,
This has only been applied on current source:/trunk (with r11169 for #12788) which will evolve in a 2.3.x release-branch soon.
This hasn't been merged into the source:/branches/2.2-stable (2.2.x) release-branch which E... -
00:23 Feature #9850: Differentiate shared versions in version-format custom field drop-downs by prepending its project name
- Mischa The Evil wrote:
> Note: the patch in note-7 does not prepend project names to custom field values in the custom field column on the issue list. This is the same behavior as currently implemented for the target version column. It ...
2013-02-15
-
23:44 Patch #13068: Allow plugins to generate test coverage reports on MRI 1.9
- I can't get this to work anymore :( now fails (trunk r11399) with:
-
23:12 Defect #13185: Redmine claims RMagick is not available
- did you included rmagick bin directory in system path?
-
21:04 Defect #13185: Redmine claims RMagick is not available
- As you see rmagick is included: attachment:bundle_show.png
Any idea, why redmine does not recognize it? -
17:29 Defect #13185: Redmine claims RMagick is not available
- Filou Centrinov wrote:
> Image thumbnails are created in redmine, so rmagick is working too.
Thumbmails are generated using shell ImageMagick command, not using rmagick gem.
> ...
Rmagick mustn't be included in your bundle, you ca... -
16:34 Defect #13185 (Closed): Redmine claims RMagick is not available
- The gem rmagick (2.13.1) is installed. I checked it with
-
23:10 Feature #10926 (Closed): Version custom field should display the project name in the combo box
- Maher Gamal wrote:
>> [...]
> ...
Mischa The Evil wrote:
> [...] so excluding the roadmap 'thingy' as described in #note-3) [...]
Actually, the project name *is* already prepended to shared versions displayed on the Roadmap view wi... -
19:00 Defect #13188 (Closed): Forms are not updated after changing the status field without "Add issues" permission
- I noticed that after changing the status field, the screen is updated, according to the workflow configuration. However, I noticed that sometimes the screen is not updated as expected. I found out that this behaviour occurs when I am a u...
-
18:52 Feature #10121: Watchers - Add Group / Role
- Duplicates #4511 I think
-
18:25 Feature #13187 (Closed): BUS/ARIA KONECRANES PRO PARTNER 276892
-
18:07 Feature #13187 (Closed): BUS/ARIA KONECRANES PRO PARTNER 276892
- BUS Needs to show the same amount of licenses as Aria.
Total licenses- 6600
ARIA ID# 22104588 -
17:57 Defect #13186 (Closed): Aria/Bus Not connecting KoneCranes
- Not the right tracker.
-
17:38 Defect #13186 (Closed): Aria/Bus Not connecting KoneCranes
- Hello! KoneCranes Pro Partner ID# 276892 is showing 6600 licenses in ARIA but showing 18,656 in BUS. The correct amount should be the 6,600.
-
16:25 Defect #13138 (Closed): Generating PDF of issue causes UndefinedConversionError with htmlentities gem
- Committed in trunk r11399 and 2.2-stable r11400, thanks.
-
13:34 Defect #13138: Generating PDF of issue causes UndefinedConversionError with htmlentities gem
- I think to this probrem caused by htmlentities gem on ruby 1.9.3
Redmine PDF export don't use htmlentities gem, now.
I wrote htmlentities gem delete patch. -
14:32 Patch #5379 (Closed): Updated Polish translation for 0.9.4 / trunk
- Thank you for your pointing.
-
14:12 Patch #5379: Updated Polish translation for 0.9.4 / trunk
- Please close this issue. It was fixed with #7202.
-
14:31 Feature #5816: New issue initial status should be settable in workflow
- It should be done, I think the implementation proposed by Norbert in the first place is indeed the best one.
-
14:20 Feature #5816: New issue initial status should be settable in workflow
- +1
-
14:30 Defect #12309 (Closed): rfpdf fails to include htmlentities gem, even when installed, thus potentially corrupting pdf output
- As #13138#note-4, this issue is duplicate.
-
14:17 Feature #5991: Tracker should have it's own default issue status
- +1
-
14:08 Defect #13184: 500 internal server error when changing tracker
- If you need more informations, this is a previous issue i had:
http://www.redmine.org/issues/12861
-
14:07 Defect #13184 (Closed): 500 internal server error when changing tracker
- Hi,
I can't change tracker, when i click on one of my (custom) tracker it doesn't load.
I got that in Firebug console:
POST http://IP:3000/projects/test/issues/new.js 500 Internal Server Error jquery...6014899 (ligne 4)
And... -
14:04
Feature #13183 (Closed): add wiki format to custom issue fields (text areas) optionally
- We defined some custom fields into the issues.
One is a info for requirement documents for our developpers.
We enter the path and filename of the documents there becauser we handle these documents inside a svn repo.
Actually there is ... -
12:37 Defect #8317: Strip whitespace from integer custom field
- In my opinion this is more an feature request than an defect because the field work like expected.
-
10:26 Feature #13182 (New): Activity page should display changes of the defined versions
- e.g. newly defined or deleted versions, renames or other edits.
-
10:09
Feature #12587: Notify for relation changes
- Johannes Wienke wrote:
> It would be nice if email notifications would also be sent for relation changes of issues.
> ...
+1
Also changes of relations should appear in a ticket's history! -
09:34 Defect #12287: Time entries of private issues are visible by users without permission to see them
- What status is this issue?
-
09:29 Feature #13175 (Closed): Possibility to define the default enable trackers when creating a project
- Feature added in r11394.
-
09:12 Defect #13169: Accessing issue's attachments error - 404 - The page you were trying to access doesn't exist or has been removed.
- It's point 4 of [[RedmineUpgrade#Step-3-Perform-the-upgrade]].
-
08:28 Defect #13169: Accessing issue's attachments error - 404 - The page you were trying to access doesn't exist or has been removed.
- Cheers.
It appeared that there was not file. I though that files were hold directly in the database.
During migration I didn't move the files from the files directory. It would be good to add such info in the upgrade/migration manual. -
09:05 Patch #13152: Locale file for Azerbaijanian language
- There are many untranslated words in trunk.
source:trunk/config/locales/az.yml@11393#L1156
And please translate this jstoolbar-az.js.
source:trunk/public/javascripts/jstoolbar/lang/jstoolbar-az.js@11393 -
07:56 Patch #13152: Locale file for Azerbaijanian language
- We have translated untranslated strings at the end
-
09:03 Feature #12789: Redmine - design study
- If a info box is showed, how is layout and orientation shall be configurable.
For example see "plugin redmine_blocks_layout":https://github.com/tastapod/redmine_blocks_layout which offers such feature.
Additionally there shall vbe plug... -
04:20 Feature #12789: Redmine - design study
- Project Overview: Yes, ticket box to the right is nice, because i don't use news (box). ...but may be not everybody is happy about this :-)
History Overview: Make it possible to set a default. Make it possible to show and hide tabs. A... -
08:49 Feature #13174 (Closed): Raise group name maximum length to 255 characters
- Feature added in r11392.
-
07:24 Patch #13181 (Closed): Bulgarian translation of jstoolbar-bg.js
- Committed in trunk r11390 and 2.2-stable r11391, thanks.
-
06:37 Patch #13181 (Closed): Bulgarian translation of jstoolbar-bg.js
- One label was left untranslated, here is its translation:
* jsToolBar.strings['Preformatted text'] -
06:25 Feature #12586: How to add Header logo in pdf while exporting wiki pages into pdf format
- Ok, anyway thanks.
-
06:22 Feature #12586: How to add Header logo in pdf while exporting wiki pages into pdf format
- satya B wrote:
> We want to avoid such table break into pages and if the table doesn't fit into current page it should automatically start from new page as like image files.
I don't know how to do it.
-
06:12 Feature #12586: How to add Header logo in pdf while exporting wiki pages into pdf format
- No, Here is the requirement, When a table starts from middle of the pdf page and if the table length is more then that page then the table will continue to the next page.
We want to avoid such table break into pages and if the table... -
06:05 Feature #12586: How to add Header logo in pdf while exporting wiki pages into pdf format
- satya B wrote:
> Hi Toshi,
> ...
Do you mean #11987? -
04:57 Feature #12586: How to add Header logo in pdf while exporting wiki pages into pdf format
- Hi Toshi,
I am trying to prevent table break into pages while converting wiki to pdf formate.
But I am unsuccessful, Is it possible to prevent table break in pdf?
If so which part of the redmine code does this, I went through few... -
05:20 Feature #824: Add "closed_on" issue field (storing time of last closing) & add it as a column and filter on the issue list.
- Henrique Bastos wrote:
> What would happen if you reopen the issue?
Always show the date of last closed status. If never has been closed before, don't show any date.
+1 -
02:24
Feature #824: Add "closed_on" issue field (storing time of last closing) & add it as a column and filter on the issue list.
- Two things to add here:
# I agree with leaving a closed field populated even after reopening. Requiring an extra filter is added robustness, not tedium, and allows you to rapidly filter issues that were previously closed regardless of... -
04:40 Patch #7202 (Closed): Polish translation for v1.0.4
- Committed in trunk r11376 and r11377, thanks.
-
00:39 Patch #7202: Polish translation for v1.0.4
-
03:40 Feature #13176: Possibilty to define a "mask" in a field of type "Text"
- I don't really understand. You need a text mask? So you can use regular expressions. You don't want that the user forget to fill the field? So you can set this field to "required".
-
02:09 Feature #11313: Automatic closing of resolved issues
- For "Resolution: Cant reproduce" this feature would be also helpful. A suitable delay time might be 90 days.
-
02:05 Feature #10568: Real-Time Collaborative Editor Wiki
- I have been looking for some solutions, I found a javascript library which could add this feature using Operational Transformation but it would require a node.js server. It is simple to use and can be found at http://sharejs.org/