Activity
From 2016-06-05 to 2016-06-07
2016-06-07
-
18:35 Feature #23006: Add "Edit" link to the issues list to open edit mode directly
- If you right-click on an issue from the issue list, there is an edit option in the context menu.
-
17:48 Feature #23006 (Closed): Add "Edit" link to the issues list to open edit mode directly
- It would be great if you/we are able to open an issue directly in edit mode from the list of issues.
If this already exist, please apologize my google capabilities -
15:23 Feature #22923: Export Wiki to ODT
- We have just released html2odt v0.3.3, which addresses all problems, that came up during your tests.
The only problem remaining would be the speed issues, you saw. But I am afraid, that I cannot isolate and reproduce those without fur... -
15:17 Patch #23003 (Closed): Bulgarian translation for 3.1-stable
- Committed in trunk, 3.3-stable, 3.2-stable, and 3.1-stable.
-
14:14 Patch #23003 (Closed): Bulgarian translation for 3.1-stable
- From #23000.
-
15:16 Patch #23000 (Closed): Bulgarian translation (r15472)
- Committed, thanks.
Could you translate this?
source:trunk/public/javascripts/jstoolbar/lang/jstoolbar-bg.js@15317 -
07:27 Patch #23000 (Closed): Bulgarian translation (r15472)
- Translated several labels, settings, etc; ordered as in en.yml.
-
14:31 Patch #14318: Watchers Alerted To Changes But Cannot See Issues (potentially)
- There's ongoing discussion in #8488.
But for those landing here in this ticket I can confirm @allow_watchers_and_contributers_access_to_issues_3.2.0.patch@ works well for @3.2.3.stable.15464@ -
14:29 Feature #8488: Create an 'Involve' mechanism to private issues
- For those of you who need the functionality right now, I suggest to use the patch @allow_watchers_and_contributers_access_to_issues_3.2.0.patch@ by Fabrizio Sebastiani from #14318#note-22. It works well for @3.2.3.stable.15464@.
Howev... -
13:31 Feature #8488: Create an 'Involve' mechanism to private issues
- _Go MAEDA wrote:_
> So we should think different approach.
Okay, agreed. But Redmine really needs a solution for that!
----
_Tobias Fischer wrote:_
> ...
While testing the patch @private_issue_watchers_3.1.x.diff@ with Redmine... -
12:55 Feature #8488: Create an 'Involve' mechanism to private issues
- Tobias Fischer wrote:
> Hang Xie wrote:
> ...
I want this feature, but I think any patches that uses watchers for access controlling purpose would not be accepted for now.
The following is Jean-Phillippe Lang's comment from #7412#... -
11:08 Feature #8488: Create an 'Involve' mechanism to private issues
- Hang Xie wrote:
> patch for 3.1.x (working on 3.1.1 and 3.1.2 )
I can confirm that this patch also works for @3.2.3.stable.15464@ and should be included as a feature in the next release.
This would be very useful! -
11:07 Feature #9330: Watchers can not see the ticket status, if their role is set to only own or assigned tickets.
- I can confirm the patch @private_issue_watchers_3.1.x.diff@ in #8488 solves this issue.
-
10:07 Feature #19937: Copy Time entry or make One Time entry for date range Redmine
- Good idea. We are using Redmine to setting a holiday period. It feature would reduce the time.
2016-06-06
-
18:16 Feature #18560: Show issues with custom field of type Version as related issues in the Roadmap
- This issue appears very different from the issue #20100 . However, the same solution can follow.
Basically, you can have a 'custom field' "Type" for each version. And then, when you define any other custom field (for issue or otherwi... -
18:16 Feature #20100: Custom version field that allows filtering versions in the list of options shown by "version's attached custom field" values
- This issue appears very different from the issue #18560 . However, the same solution can follow.
Basically, you can have a 'custom field' "Type" for each version. And then, when you define any other custom field (for issue or otherwi... -
18:16 Feature #17962: Filterable versions in dropdowns (target version and custom version fields on issues)
- As I stated in other issues -
> Basically, you can have a 'custom field' "Type" for each version. And then, when you define any other custom field (for issue or otherwise) which is of type version - it should ask for criteria as "fie... -
18:16 Feature #685: New Custom Field "Found in Version"
- Well looks like the demand of this is really there with multiple issues.
But it can be achieved: (As I noted in other issue)
> Basically, you can have a 'custom field' "Type" for each version. And then, when you define any other ... -
16:43 Feature #685: New Custom Field "Found in Version"
- Essentially, it is not just about the "Found in Version". If there are custom fields based on version - we need qualifiers whether the fields are open, locked or closed.
I guess it would be too much to ask for that they will be restr... -
18:16 Feature #14250: BugTracker enhancement: allow to create a custom field for "occours in version" - end of Life
- Well looks like the demand of this is really there with multiple issues.
But it can be achieved: (As I noted in other issue)
> Basically, you can have a 'custom field' "Type" for each version. And then, when you define any other ... -
17:43 Feature #17907: Give 'version' another meaning
- This is indeed necessary for using Redmine for non-software projects. This should be considered when we are making larger over haul in versions under issue #13387.
Add related #13387 -
17:32 Feature #22959: Customize "Related issues" list in version detail
- If we bring up all functionality that Issue query page has - essentially having a page for version is lost! The version page lists various other details (related to project management aspects etc.) which is why that page is not merely a ...
-
15:27 Feature #22959: Customize "Related issues" list in version detail
- Thanks Haihan Ji for your reply.
That is something we do, but it implies an extra step each time we create a version (setting up a query with the desired result, and put it in the wiki of the version) and more importantly, each time w... -
17:23 Feature #21249: Ability to filter issues by attributes of a version custom field (e.g. release date)
- +1
-
17:20 Feature #22790: Relation between main project version and sub-projects versions
- +1. This is almost same as #8991. Can also be linked to #13387
-
17:14 Feature #22997 (Closed): Administrative calendar
- Not only Sat. and Sun don't work. For example.
2016-06-09 is the Dragon Boat Festival of China.
That mean's Chinese don't work from 2016-06-09 to 2016-06-11,
but they have to work at 2016-06-12 (Sunday).
So, I hope admin can set whic... -
17:01 Feature #18126: Allow setting up version hierarchy
- Add related - #8991
-
17:00 Feature #8991: Nested versions for projects with sub-projects
- Sebastian Hucke wrote:
> M. A. wrote:
> ...
This plug-in is very good and useful. However, it introduces entries 'milestone' which is a different entities. Here we are talking about versions related to version - a functionality require... -
16:58 Feature #8991: Nested versions for projects with sub-projects
- +1 very useful.
-
16:57 Feature #4585: Move a Version from one project to another
- Tyler Rose wrote:
> There is a fairly easy work around without having to go into the database ...
> ...
Not at all! First off, there are often lot of custom fields associated with versions that won't be classified automatically. The ve... -
16:47 Feature #21290: Watch on version
- In fact, a more useful watch facility for version is if any issue got added or removed in the given verison. If I am a QA responsible to test a given version - I may not be author or assignee (receiving mails by default) - so I would lik...
-
16:34 Feature #22923: Export Wiki to ODT
- Thanks a lot for testing this patch/feature.
I have just set up a Windows development machine to verify your feedback:
> * exporting the whole wiki doesn't respond/is too slow (had to kill ruby after 15 minutes), we should probably... -
12:51 Feature #22923: Export Wiki to ODT
- Jan from Planio www.plan.io wrote:
> We hadn't tested it on Windows though which it seems you have used for your tests, correct?
Correct, ruby 2.0.0p481 (2014-05-08) [i386-mingw32] -
12:36 Feature #22923: Export Wiki to ODT
- > I tested the patch on a copy of the Redmine wiki:
Thank you for testing it. The long response times seem quite odd. It works quite fast (also with larger wikis) for us. For comparison, you could try on a "new Planio account":https:/... -
12:30 Feature #22923: Export Wiki to ODT
- I tested the patch on a copy of the Redmine wiki:
* exporting the whole wiki doesn't respond/is too slow (had to kill ruby after 15 minutes), we should probably disable this option. In comparaison, exporting every pages individually t... -
03:00 Feature #22923: Export Wiki to ODT
- I tested this patch with LibreOffice Mac and Word 2016 for Mac, works fine. I think it is very useful to write documents based on wiki contents.
@Jan-Philippe, could this be included in 3.3.0?
-
16:02 Feature #15880: Consistent, global button/menu to add new content
- Tobias Fischer wrote:
> And what about support for third-party themes which use a vertical nav menu?
I am not aware of any currently-supported themes with vertical project nav. The only one I can remember is "Pixel Cookers":http://ww... -
15:53 Feature #15880: Consistent, global button/menu to add new content
- the fury wrote:
> Speaking of vertical nav menus, how would this "add new" menu work when on mobile devices, with the responsive stuff?
The "+" menu does not show in the responsive menu (yet). However, with the "New issue" tab being ... -
15:46 Feature #15880: Consistent, global button/menu to add new content
- Tobias Fischer wrote:
> Also bad UX in terms of accessibility.
> ...
Btw., I have moved the access keys to the (always visible) "new issue" link within the "+" menu. This way, the Ctrl+Alt+7 shortcut will work even if the "New issue" t... -
15:24 Feature #15880: Consistent, global button/menu to add new content
- Thanks Jan for working on this. I tried out this patch.
It is a awesome feature. We can access every "Add" screen from everywhere by one click. I am sure that UX of Redmine is significantly improved by this feature. Probably I will ne... -
14:26 Feature #15880: Consistent, global button/menu to add new content
- I have rebased the patch series (minus the things already committed by Jean-Philippe) on the current trunk.
Ready to be committed :-) -
15:26 Feature #17601: Enable Gravatar icon on redmine.org
- Ilya Ishmatov wrote:
> Hi, I'm worry about the gravatar tracks movement on internet.
> ...
FTR: #17641 -
12:57 Feature #22995 (New): Replace ImageMagick thumbnail creating with GD Graphics Library aka libgd
- Currently image thumbnails are created using shell outs to ImageMagick's convert tool.
There are multiple reason, why this might need to be changed. I do not want to list them here though, since they are largely fueled by "FUD":https:... -
12:57 Feature #10117: 'Permission - Project - Manage Groups' required
- append requirement details:
* PM can create/modify/delete local group in Project/Setting/Member page (maybe other project's page).
* PM can add member of project team to local group. If a user is not project member, he can't be adde... -
12:47 Feature #22993: Deadline
- Haihan Ji wrote:
> Dade Murphy wrote:
> ...
I apologize. I redmine only acquainted. I understand enough to console simply register once RAILS_ENV = "production" rake redmine: send_reminders and warning of "deadline" will be sent to all... -
12:32 Feature #22993: Deadline
- Dade Murphy wrote:
> Greetings. Setting mail notification about the deadline, overdue tasks. Also, the ability to move it.
I think you can add @rake redmine:send_reminders@ to cron task.
It's not a new feature. -
12:12 Feature #22993 (Closed): Deadline
- Greetings. Setting mail notification about the deadline, overdue tasks. Also, the ability to move it.
-
12:44 Feature #22987 (Closed): Ruby 2.3 support
- Ruby 2.3 added to 3.3-stable test environments.
-
06:11 Feature #22987 (Closed): Ruby 2.3 support
- Missing Ruby 2.3 in CI matrix 3.3-stable.
http://www.redmine.org/builds/index.html -
12:43 Feature #7839 (Closed): Limit trackers for new issue to certain roles
- Implemented as part of #285 in 3.3.0.
-
12:42 Feature #285 (Closed): Tracker role-based permissioning
- 3.3.0 will support tracker based permissions for issue tracking. You will be able to limit the trackers for which a role is allowed to view, create, edit or delete issues.
-
12:42 Feature #3726 (Closed): Trackers per Role
- 3.3.0 will support tracker based permissions for issue tracking. You will be able to limit the trackers for which a role is allowed to view, create, edit or delete issues.
-
12:30 Patch #22979: German translations for 3.3 (for r15435)
- Tobias Fischer wrote:
> @Toshi MARUYAMA: I don't understand? Why do you remove the target version? It's already committed in trunk and 3.3-branch?
"Target version" becomes "Changelog".
It is very annoying there are many translation ... -
09:22 Patch #22979: German translations for 3.3 (for r15435)
- @Jean-Philippe: You're welcome! Thanks for comitting :)
@Toshi MARUYAMA: I don't understand? Why do you remove the target version? It's already committed in trunk and 3.3-branch? -
07:03 Patch #22979: German translations for 3.3 (for r15435)
- This is only for new release translation, so I remove target.
-
12:28 Feature #22913: Auto-select fields mapping in Importing
- Append Unit Test Code.
-
12:18 Patch #22991 (Closed): Japanese translation update (r15472)
- Committed in trunk and 3.3-stable, thanks.
-
08:13 Patch #22991 (Closed): Japanese translation update (r15472)
- Translated the following strings:
* error_no_tracker_allowed_for_new_issue_in_project
* label_tracker_all
-
12:06 Patch #22989 (Closed): Czech translation for 3.1-stable
- Committed in 3.1-stable.
-
06:24 Patch #22989 (Closed): Czech translation for 3.1-stable
- From #22974.
-
12:05 Patch #22988 (Closed): Czech translation for 3.2-stable
- Committed in 3.2-stable.
-
06:23 Patch #22988 (Closed): Czech translation for 3.2-stable
- From #22974.
-
11:58 Patch #22983 (Closed): Simplified Chinese translation for Revision 15449
- Committed in trunk and 3.3-stable, thanks.
-
09:22 Defect #22831: Rest api no longer return estimated time ,hours spent for master tickets
- Using rest api issues
Environment:
Redmine version 3.2.1.stable.15362
Ruby version 2.1.9-p490 (2016-03-30) [x86_64-linux]
Rails version 4.2.5.2
Environment ... -
07:03 Patch #22974: Czech localization patch
- This is only for new release translation, so I remove target.
-
01:56 Patch #22421 (Closed): Updated Korean locale data
- Closing as a duplicate of #22506.
Thanks for translating.
2016-06-05
-
12:33 Feature #7839: Limit trackers for new issue to certain roles
- yes, just as Radek said.
I think it should according by users or roles to control whether to create or edit or view the issues with trackers?
Radek Chan wrote:
> I tested the plugin. User is still able to create a new issue, but ... -
09:08 Defect #22932 (Closed): "Group by" row from issues listing has the colspan attribute bigger with one than the number of columns from the table
- Committed, thanks for this fix.
-
03:44 Defect #22932: "Group by" row from issues listing has the colspan attribute bigger with one than the number of columns from the table
- Confirmed the problem in Safari and Chrome. No problem in Edge and Firefox.
-
04:00 Feature #22843: Change the value of "pre" button in Markdown toolbar from "~~~" to "```"
- '~~~' is also correct Markdown and works as expected on my environment.
http://spec.commonmark.org/0.25/#code-fence -
03:13 Feature #22913: Auto-select fields mapping in Importing
- Very interesting feature.
Could you add tests? Tests are required to be merged into the core. -
02:55 Feature #22982 (Closed): PM can manage local group in Project.
- I found a very similar request #10117. Closing as a duplicate.