Activity
From 2013-12-06 to 2013-12-08
2013-12-08
-
14:55 Defect #15624 (Closed): Redmine fields inside mail notifications should be mime-encoded
-
12:44 Defect #15623 (Closed): Timelog filtering by activity field does not handle project activity overrides
- While filtering timelogs on all projects, it seems that filtering does not work as expected.
In provided screenshot you can see that filtering on Activity field by excluding values, generates result that also includes excluded values. ... -
10:55 Feature #12579: Ability to assign issues to multiple users
- This plugin is related: "Redshares":/plugins/redshares
-
10:55 Feature #408: Assign a task to multiple users
- Do not post to closed issue.
Current duplicate issue is #12579. -
10:17 Feature #5159: Ability to add Non-Member watchers to the watch list
- OK thanks. Filed #15622
-
10:12 Feature #5159: Ability to add Non-Member watchers to the watch list
- Daniel Hochman wrote:
> No, this is a bug. I am having the same issue as Beni and we are no longer on bitnami stack. This issue needs to be re-opened as a bug. You cannot add watchers who are not members of the project after issue creat... -
09:41 Feature #5159: Ability to add Non-Member watchers to the watch list
- No, this is a bug. I am having the same issue as Beni and we are no longer on bitnami stack. This issue needs to be re-opened as a bug. You cannot add watchers who are not members of the project after issue creation.
-
09:38 Feature #5159: Ability to add Non-Member watchers to the watch list
- Beni Bilme wrote:
> We are using bitnami redmine stack for redmine 2.3.3, and watchers function is not working unless the watcher is project member.
You need to search in text box. -
10:17 Defect #15622 (Closed): Unable to add watcher who is not a member of the project
- The feature described in #5159 (Ability to add Non-Member watchers to the watch list) is confirmed as not working in Redmine 2.3.1 and 2.3.3
You can only add people who are members of the given project. -
00:59 Feature #1853: Make Projects truly independent of each other
- @Beni Bilme Have you considered spinning up multiple instances of redmine for each department?
-
00:38 Feature #1853: Make Projects truly independent of each other
- +1
We have tried to customize the redmine for a 60 people organization. There are people with different profession. We are using redmine to track tasks. However we had to create lots of different trackers and custom fields. We had to gi...
2013-12-07
-
22:37 Feature #5159: Ability to add Non-Member watchers to the watch list
- We are using bitnami redmine stack for redmine 2.3.3, and watchers function is not working unless the watcher is project member.
-
22:25 Feature #12579: Ability to assign issues to multiple users
- I work in a non profit organization. In the my organization, we have different departments/sections under a director. Directory opens up an issue that will be handled by the organization. An issue usually involves multiple sections/depar...
-
22:24 Feature #408: Assign a task to multiple users
- I work in a non profit organization. In the my organization, we have different departments/sections under a director. Directory opens up an issue that will be handled by the organization. An issue usually involves multiple sections/depar...
-
22:10 Feature #7774: Sub groups or Multi-level groups
- +1
I work in a non-profit organization and my organization is really in need of this feature -
13:39 Defect #15612: Long message on update in journal_details where prop_key = 'send_notification'
- Github mirror stopped r12243.
Because it reads rubyforge SVN.
https://github.com/edavis10/redmine/commit/2e1f80dcdede1fc58f93b58ea7b2256aacf6ec93 -
12:23 Defect #15612: Long message on update in journal_details where prop_key = 'send_notification'
- i've found bug. Problem in different db structure. And i'm not surprised, because till to version 2.4 redmine from github worked with notifications via activerecord callbacks, but redmine that was in bitbucket works on deprecated activer...
-
02:05 Defect #15612 (Closed): Long message on update in journal_details where prop_key = 'send_notification'
- I added test some tests and tests pass.
-
09:52 Defect #15590 (Closed): Database migration error from 2.1.4 to 2.4.1
- This error means that your database is not preperly upgrade. Please read [[RedmineUpgrade]].
-
03:49 Defect #15617: Regional (i.e. sub) localization not correctly supported
- Fixed by correcting "en" to "en-GB" in locale file as advised in related ticket.
Thanks Toshi
-
03:34 Defect #15617: Regional (i.e. sub) localization not correctly supported
- Clearing cache has no effect (& isn't a feasible solution on a running production site)
-
03:18 Defect #15617 (Closed): Regional (i.e. sub) localization not correctly supported
- Duplicate with #12900.
Try cache clear. -
03:11 Defect #15617 (Closed): Regional (i.e. sub) localization not correctly supported
-
01:06 Patch #15616 (Closed): Add a permission setting allowing members to delete their own projects
- In order to delegate project subtrees to managers that are not admins, I found useful to implement this patch. It adds an extra permission setting that allows authorized users to delete their projects. (I could only add french/english tr...
2013-12-06
-
17:13 Defect #15612: Long message on update in journal_details where prop_key = 'send_notification'
- simple way to prove it: add
@puts "*"*80
puts "run deliver_issue_add"
puts "*"*80@
in send_notification method, and try to update existing task, you'll see what i'm talking about, right in log
(test in redmine with plugins, and t... -
17:07 Defect #15612: Long message on update in journal_details where prop_key = 'send_notification'
- yeah, thanks for link, i saw the code, but my question is "why deliver_issue_add runs even after i save existing issue, not create a new one?". I know how it should be.
-
17:04 Defect #15612 (Needs feedback): Long message on update in journal_details where prop_key = 'send_notification'
- Ilya S wrote:
> I see, that deliver_issue_add should calls only after_save Issue instance, but behaviour differs a bit.
Issue#after_save does not call "send_notification".
Only "after_create" in Issus class calls "send_notification"... -
16:44 Defect #15612 (New): Long message on update in journal_details where prop_key = 'send_notification'
-
16:34 Defect #15612: Long message on update in journal_details where prop_key = 'send_notification'
- +1. Same problem here. Update redmine core from 2.3.3 -> 2.4.1 and this bug appear.
And one more thing: even when i update existing task update calls deliver_issue_add method, and deliver_issue_edit. If i create a new one, then calls ... -
14:34 Defect #15612 (Closed): Long message on update in journal_details where prop_key = 'send_notification'
- Please contact plugin author.
-
11:51 Defect #15612 (Reopened): Long message on update in journal_details where prop_key = 'send_notification'
- Hello
I swear NO.
I guess the problem is that I have installed a plugin and removed it just be deleting the folder... ;(((
What could cause this ? It's really annoying since it makes items unreadable...
thanks a lot ! -
04:40 Defect #15612 (Closed): Long message on update in journal_details where prop_key = 'send_notification'
- There is no "send_notification" field on Redmine.
It is in ChiliProject.
https://github.com/chiliproject/chiliproject/commit/614bad89a5e02b66776fa16f5dce341821650c7b -
16:30 Feature #15615 (New): customise the mail with a specific template
- I would like to change the template of redmine's mail by a specific template that include logo in the footer. and filter some fields to be send or not, this is very useful when we don't want some roles to see these fields.
-
16:22 Feature #6176 (Closed): Email Notifications per project
- Duplicate with #4462.
-
14:50 Defect #15613 (Closed): 'Add watchers' within the new issue reveals all the accounts
- Duplicate with #15123.
-
09:27 Defect #15613 (Closed): 'Add watchers' within the new issue reveals all the accounts
- Hi,
'Add watchers' within the new issue reveals all the Redmine accounts, not only the project accounts. We consider it as a security issues and we had to remove the link from issue page.
Version:
We are using Redmine 2.3.2.stabl... -
10:07 Feature #12005: Mightful workflow field enhancement: hide
- Please have a look at version 2.4 which resolved issue #5037 _"Role-based issue custom field visibility"_
In 2.4 you are now able to hide certain fields based on a role... -
08:28 Feature #12005: Mightful workflow field enhancement: hide
- in Redmine 2.3.3, i had an error ( undefine method reject! in query.rb so, i changed @available_columns.reject! to available_columns.reject! and it works fine only in show information. but in edit or mail, we still find the hidden fields.
-
07:02 Feature #2829: Ability to set default search filter for Issues
- Very much need!
-
05:01 Defect #5695 (New): Problem with assignable users in the report page
-
04:22 Defect #15610 (Closed): How to create Project.
- This is tracker for Redmine. Users have no right to create projects.
If you try it, please use http://demo.redmine.org or http://m.redmine.org.