Activity
From 2016-03-28 to 2016-03-30
2016-03-30
-
22:57 Feature #1077: ICS view of Calendar
- Done! I installed this one https://github.com/buschmais/redmics and working fine. Thanks any way.
-
21:34 Feature #1077: ICS view of Calendar
- Anything like that for redmine 3.x?
Redmine version 3.2.1.stable
Ruby version 2.1.8-p440 (2015-12-16) [x86_64-linux]
Rails version 4.2.5.2
Environment produ... -
16:34 Patch #22345: Trackers that have parent_issue_id in their disabled_core_fields should not be selectable for new child issues
- Confirmed.
Setting target version to 3.3.0. Thanks for the patch.
!screenshot-without-the-patch.png!
-
08:13 Patch #22345 (Closed): Trackers that have parent_issue_id in their disabled_core_fields should not be selectable for new child issues
- When the user views an issue and clicks the link to add a new child issue, and the project has some trackers where the @parent_issue_id@ field is disabled, the resulting new issue form for the child issue still presented those trackers f...
-
16:10 Feature #11361: Custom Field Groups, and User Specific Fields
- +1
-
13:33 Feature #11361: Custom Field Groups, and User Specific Fields
- +1
-
15:20 Feature #18858: Custom Fields - Sort/Order
- Awesome! Looking forward for 3.3.0.
-
15:03 Feature #21930: Change priority depending on the due date
- Hi, I'm interesting about this features.. I have the 2.3.0 version on my server and this could be a important plugin if exists.
At the moment I can extract priority/start date/due date and I change the priority with a sql script... bu... -
14:48 Feature #22352 (New): Manage customer fields of plugins
- Redmine plugins sometimes add new fields in Redmine (in issues or other part of Redmine). It's obviously possible to add them in custom fields but in that case, administrators are not informed that the custom field is required for a plug...
-
14:14 Feature #6631: Provide security (e.g. display only) for custom fields
- This is already available through /workflows/permissions.
-
13:45 Feature #11161: Custom fields by role
- In /workflows/permissions, you can already manage the "Read-only" and "Required" state for custom fields. The visibility is not managed for other fields too. I use redmine_workflow_hidden_fields plugin to manage this.
-
13:36 Feature #3058: Show issue history using tabs
- Hi,
During this implementation, Can you please also consider to provide a hook.
We have already defined some tabs in the ticket history region through a plugin development(currently overriding the corresponding partial).
Thanks. -
13:34 Feature #13839: Custom fields presentation - Group custom fields in section / panel
- +1
-
13:28 Feature #16084: We would like to order the appearance of custom field
- +1
-
12:57 Defect #19173: Trac Migrate Script with Redmine 3.0
- Any solutions for this issue from Senthil?
-
12:38 Defect #5156: Bulk edit form lacks estimated time field
- Added tests: attachment:feature-5156-v2.diff
-
12:16 Defect #5156: Bulk edit form lacks estimated time field
- Here's a patch for Redmine 3.2.1.devel.15287: attachment:feature-5156.diff
-
05:44 Defect #5156: Bulk edit form lacks estimated time field
- +1 and I think this feature should be implemented.
Setting target version to "Candidate for next major release". -
11:09 Feature #973: Assign different status sets and workflows for separate projects
- +1 I would also require this kind of feature where workflow can be defined at a project level. Since we have project that follow different workflows and statuses
-
09:37 Feature #9787: Get issue history
- You can use GET /issues/2.xml?include=attachments,journals to get the history details.
-
06:24 Patch #14318: Watchers Alerted To Changes But Cannot See Issues (potentially)
- Fernando Hartmann wrote:
> Takenori TAKAKI wrote:
> ...
+1
2016-03-29
-
20:39 Defect #22342: When copying issues to a different project, subtasks /w custom fields not copied over
- A work around is to copy issues with subtasks using custom fields to the same project and then move the issues to another project.
-
20:37 Defect #22342 (Closed): When copying issues to a different project, subtasks /w custom fields not copied over
- My environment:
-
20:09 Patch #14318: Watchers Alerted To Changes But Cannot See Issues (potentially)
- Takenori TAKAKI wrote:
> I also really want to see this in 3.3 relase.
+1 -
04:14 Patch #14318: Watchers Alerted To Changes But Cannot See Issues (potentially)
- Go MAEDA wrote:
> Wonderful feature. I really want to see this in 3.3 relase.
> ...
I have updated the patch for below:
* Compatible with latest trunk (r15287)
* Added tests
I also really want to see this in 3.3 relase. -
15:16 Feature #22156: Is there a way to set the filter status to be “Any” by default?
- Attached patch file
-
15:09 Feature #22156: Is there a way to set the filter status to be “Any” by default?
- Added patch which will set the filter status as any instead of open.
-
14:11 Patch #22337: Ignore settings.yml in git/hg for cleaner repository updates
- Thx, sorry for the trouble
-
13:57 Patch #22337 (Closed): Ignore settings.yml in git/hg for cleaner repository updates
- Cy topia wrote:
> I see, then i totally got it wrong.
> ...
This will change on Web UI. -
13:48 Patch #22337: Ignore settings.yml in git/hg for cleaner repository updates
- I see, then i totally got it wrong.
Where do you edit -
13:45 Patch #22337: Ignore settings.yml in git/hg for cleaner repository updates
- Cy topia wrote:
> Sorry, conflict was the wrong word.
> ...
Why did you edit *settings.yml*?
> So when i re-checkout this file or stash the repository, all my changes in the configuration file will be lost.
> ...
database.yml and a... -
13:38 Patch #22337: Ignore settings.yml in git/hg for cleaner repository updates
- Sorry, conflict was the wrong word.
When I check out redmine via git/hg *settings.yml* is tracked (by git and hg), meaning as soon as I edit this file, the git/hg repository will be unclean.
So when i re-checkout this file or stash... -
13:33 Patch #22337: Ignore settings.yml in git/hg for cleaner repository updates
- Cy topia wrote:
> This is simply in order to avoid conflict when git-pulling a new Redmine version via git/hg
Why conflict happens?
-
13:31 Patch #22337: Ignore settings.yml in git/hg for cleaner repository updates
- Did you read this line?
source:tags/3.2.1/app/models/setting.rb#L229 -
13:28 Patch #22337: Ignore settings.yml in git/hg for cleaner repository updates
- The file is not modified!!
It is simply renamed to *settings.yml.example*
This is simply in order to avoid conflict when git-pulling a new Redmine version via git/hg -
13:27 Patch #22337: Ignore settings.yml in git/hg for cleaner repository updates
- -1 because source:tags/3.2.1/config/settings.yml#L19 says "DO NOT MODIFY THIS FILE !!!".
-
13:16 Patch #22337 (Closed): Ignore settings.yml in git/hg for cleaner repository updates
- Linked from github: https://github.com/redmine/redmine/pull/77
I have renamed *config/settings.yml* to *config/settings.yml.example* and ignored *config/settings.yml* in *.gitignore* and *.hgignore*.
The main reason I would like to... -
13:28 Feature #8991: Nested versions for projects with sub-projects
- M. A. wrote:
> I am also looking for this functionality.
> ...
We use a plugin to achieve this functionality: https://github.com/Coren/redmine_advanced_roadmap_v2 -
13:13 Feature #8991: Nested versions for projects with sub-projects
- I am also looking for this functionality.
Are there any news?
We have releases of projects A, B, C with all their sub-projects at the same time.
* Software 1.0 (Project Milestone)
** Software A 1.5
** Software B 3.1
** ...
* Sof... -
12:31 Patch #22336 (Closed): Revision Table does not scroll horizontally on small screens
- On small screens: While the directory listing table may be scrolled horizontally, the revision table may not. Therefore the commit message and author is not available on mobile devices.
!before.png!
The attached patch adds an @.aut... -
12:27 Feature #4806: Filter the issue list by issue ids
- From my point of view it would be usefull to filter by #, especally for documentation.
For testing I have to generate a list of fixed bugs for my testing team. When the test is done I need the list of all fixed items with the actualized... -
11:19 Feature #12444: Ability to "set as default" settings when creating users
- +1
-
11:19 Feature #16484: Add default timezone for new users
- +1
-
10:02 Defect #20882: % done: progress bar blocked at 80 in the issue list
- Yes it's just a tiny difference.
-
07:46 Feature #6914: Allow reporter to opt out from receiving email updates
- Etienne Massip wrote:
> We could simply add author to watchers list at issue creation so that author can unwatch anytime ?
I think the proposed behavior is straightforward. -
07:25 Defect #22335 (Closed): Images with non-ASCII file names are not shown in PDF
- Images with non-ASCII file names are not shown in PDF. Please see the following image. There are two embedded image "shrine.jpg" and "神社.jpg" in a issue description. But "神社.jpg" (an image with non-ASCII file name) are not shown in expor...
-
05:27 Defect #22331: bundler error: Ruby 1.9.3 = "mime-types-data requires Ruby version >= 2.0."
- Toshi MARUYAMA wrote:
> Try r15277.
Thanks! I modified @Gemfile@ to include that change and it allowed me to complete the 3.2.0 to 3.2.1 upgrade without issue. -
03:52 Defect #22331 (Closed): bundler error: Ruby 1.9.3 = "mime-types-data requires Ruby version >= 2.0."
- Try r15277.
2016-03-28
-
20:02 Feature #22332 (New): wiki id & parent_id in GET on api
- I am using the API to add and modify wiki articles. There is no way through the API to pull back the id of the wiki or the id of the parent wiki via the api. This is an issue when programatically trying to add wiki articles with a pare...
-
18:36 Defect #22331 (Closed): bundler error: Ruby 1.9.3 = "mime-types-data requires Ruby version >= 2.0."
- Error message encountered when running @bundle update@ from my Redmine installation directory:
-
14:00 Feature #3467 (Closed): Due date sort order should sort issues with no due date to the end of the list
- Closing as a duplicate of #6034.
-
12:48 Feature #22327 (Closed): Sort Projects by status and custom field values
- Having worked with Redmine for a while, I now have many projects running. Some of them are active, other are not. Nevertheless, while I can search / filter issues by their custom fields, it cannot do the same with projects. It would be r...
-
10:08 Feature #22326 (New): New 'Remaining Time' field -- NOT related to the % done
- To enable burn down charts, users should report the remaining time per task in the iteration (version). This field should be independent and should be different that the estimated time.
Typically, the estimated time is only a 'first ... -
04:32 Feature #11361: Custom Field Groups, and User Specific Fields
- +1 If this feature is implemented, it is possible for me to apply various situations.