Activity
From 2012-01-13 to 2012-01-15
2012-01-15
-
22:41 Feature #779: Multiple SCM per project
- I've just tested the new features (r8648, r8649, r8650, r8651, r8652). Great addition to Redmine.
I would like to propose these visual enhancements:
* The currently selected repository to be someway visually marked (bold, italic, or a ... -
03:43 Feature #3647: Data Import/Export System
- +1
(it seems there is no easy way to switch from sqlite3 to mysql, so a data import/export feature could take care of that.)
2012-01-14
-
21:21 Feature #8545: "get projects" REST API response should handle "include=trackers" parameter
- can we include this into Redmine 1.3.1?
-
18:59 Patch #5966: change to allow openID to use Google Apps
- there is a fix for this: http://projects.andriylesyuk.com/projects/openid-fix
why isn't this factored in?!
-
18:59 Defect #3780: Attribute exchange with OpenID providers
- there is a fix for this: http://projects.andriylesyuk.com/projects/openid-fix
why isn't this factored in?! -
18:45 Feature #1248: New Permission: Edit own issues
- +1
-
16:57 Feature #4774 (Closed): Change the hyperlink for file attachment to view and download
- Attachment links changed so that they download the file. A link to view the file is added for text files.
-
15:31 Feature #9985: Group time report by the Status field
- Thanks to have integrated it in the core.
Hope this is only the first, we are making a lot of enhancements in the company I work in. -
10:58 Feature #9985 (Closed): Group time report by the Status field
- Added in r8643.
-
13:03 Feature #1189: Multiselect custom fields
- +1
-
10:39 Defect #9996: configuration.yml in documentation , but redmine ask me to create email.yml
- Are you using "fa" language ?
2012-01-13
-
23:19 Defect #9996: configuration.yml in documentation , but redmine ask me to create email.yml
- I guess you're not running Redmine 1.3.0, 1.3 really does not care about email.yml.
Please post details according to [[SubmittingBugs]].
-
22:57 Defect #9996 (Closed): configuration.yml in documentation , but redmine ask me to create email.yml
- documentation says, that it is need to create configuration.yml
http://www.redmine.org/projects/redmine/wiki/EmailConfiguration
I created:
production:
email_delivery:
delivery_method: :smtp
smtp_settings:
tls: ... -
22:04 Defect #8325: undefined method `name' for "actionmailer":String (RubyGems > 1.6 not supported)
- Etienne Massip wrote:
> 旭 張 wrote:
> ...
I'm not a big fan of using an ancient version of RubyGems either. This can be problematic when you have multiple rails apps on the same server as Redmine. I used RVM to create a custom Ruby wi... -
20:38 Feature #9923 (Closed): User type custom fields should be filterable by "Me".
- Added in r8638.
-
20:25 Feature #2161: Time tracking code should respect weekends as "no work" days
- +10000K
-
18:32 Feature #9995 (Closed): Time entries insertion, "Create and continue" button
- This way time entries can be added day by day, for the month (for example),
without to return each time to the issue.
-
15:42 Feature #9994 (Closed): Add links in report view for users, projects, issues
- This helps to stay on the report window, and grab some specific informations in other web browsers tabs.
-
15:15 Feature #8818: Repository user-mapping with multiple email addresses
- This issue is exacerbated by the Defect #9897 which is due to the missing feature #1273. Each time there are dozens of emails we need to relink when a change requiring a resync of the repo is required.
-
13:42 Defect #9762: Closing issues with commit should be cross project
- I am also experiencing problems with this issue.
We have a main project for our framework. This framework has multiple sub projects.
We have a main project with multiple sub projects.
These sub projects use a few modules from our fram... -
13:37 Feature #9993 (Closed): Export and import all information (Database)
- Add new settings, which help me to *export* and *import* all information in Redmine (projects, issues, etc.)
Thanks -
13:12 Feature #1171: Add workflow for custom fields
- +1
-
13:06 Feature #5816: New issue initial status should be settable in workflow
- Yeah, this is a big problem for us too.
We need different status sets in our trackers, so different start and finish status per tracker. At the moment there is one start status for all tracker's
This issue is duplicated by #558
... -
13:06 Feature #558: Default & Closed statuses to be saved at workflow level
- duplicate of #5816
-
13:05 Defect #5593: Grey out workflow checkboxes for transitions to the same status
- +1
Small but easy embeddable enhancement! -
12:46 Feature #9992: Ability to filter issue subtasks in issue form
- I wish I could see only one request and all its subtasks
-
12:44 Feature #9992: Ability to filter issue subtasks in issue form
- I wish I could see only one issue and all its subtasks
-
11:26 Feature #9992: Ability to filter issue subtasks in issue form
- Or is it the ability to filter the issue list with a "Parent task" filter to get all subtasks of a specific issue?
-
11:11 Feature #9992: Ability to filter issue subtasks in issue form
- Is this OK to you?
-
10:12 Feature #9992: Ability to filter issue subtasks in issue form
- If I want look only a task with yours subtasks
-
09:46 Feature #9992: Ability to filter issue subtasks in issue form
- What filters?
-
09:37 Feature #9992 (New): Ability to filter issue subtasks in issue form
- It would be interesting to see the filters in a task and its subtasks
-
12:00 Feature #5991: Tracker should have it's own default issue status
- +1
-
11:24 Feature #9991: Estate parent task vs subtask
- #6422 or #6687 ?
-
11:12 Feature #9991: Estate parent task vs subtask
- This is a dup of another issue, don't know which one yet.
-
09:35 Feature #9991 (Closed): Estate parent task vs subtask
- I think a good feature would be the status of the related subtasks of the parent task, for example
1 parent task with 2 sub tasks
Subtask 1 new
Subtask 2 new
Parent task: new
Subtask 1 in progress
Subtask 2 new
Parent task: i... -
09:20 Feature #2035: Issue reporter should be editable
- +1
-
08:51 Defect #9940 (Closed): Branch names are truncated
- Closed as duplicate of #9824.
-
08:01 Defect #9940: Branch names are truncated
- Um.... I'm getting senile in my old age-- forgot to say a couple of things in my previous post:
I am running the latest trunk as of today. Using Ruby 2.3.14, Apache with fcgid:
About your application's environment
Ruby version ... -
07:43 Defect #9940: Branch names are truncated
- I was just about to report the same thing. This seems to be a problem with the new branch visualization feature (which is cool, BTW). All of the names are obscured in some way or another. Some of the history lines are obscured. See at...