Activity
From 2016-07-23 to 2016-07-25
2016-07-25
-
22:40 Defect #23430: I can not access a closed project Issues
- Diego Gonzalez wrote:
> Having closed the project and the Issues on it, I can not access them
Add information, to have only one project open and information is displayed correctly -
22:09 Defect #23430 (Closed): I can not access a closed project Issues
- Having closed the project and the Issues on it, I can not access them
-
17:14
Patch #23417: Make the ID column configurable in the issues listing like the other columns
- +1
Very useful patch! -
01:11 Patch #23417 (New): Make the ID column configurable in the issues listing like the other columns
- Currently, in the issues listing table, there are two "hard coded" columns:
# first column with the checkbox
# second column with the issue ID
In our custom theme, we want to have the subject in the first column in order to improve ... -
16:41 Defect #23420 (Closed): Error 500 whhen access to activity page of one project
- Please contact plugin author.
-
16:14 Defect #23420: Error 500 whhen access to activity page of one project
- Maybe a problem with my redmine tree, I don't reproduce on similar context on other machine.
-
09:22 Defect #23420 (Closed): Error 500 whhen access to activity page of one project
- Version Redmine 3.3.0.devel.15732
Access to the activity page says internal error.
The production.log says : -
16:26 Defect #23421 (Closed): Upgrade without "development" still tries to connect to "development" database
- https://www.google.com/search?q=rails+rake+default+environment
-
09:52 Defect #23421 (Closed): Upgrade without "development" still tries to connect to "development" database
- I was upgrading @3.0.1@ to @3.3.0@
I used this command: -
13:43 Defect #23425 (Closed): Wrong entries in custom fields after changing the content of the field
- Hello,
if i change the value of a custom field to a new value it doesnt change right.
After the change i have the old and the new value in the custom field.
Pictures below does show it.
Greetings,
Fridolin -
11:51 Feature #23423 (New): Add categories to custom fields
- Working with lots of projects which uses many different custom fields makes Redmine really hard to administrate because we currently have a raw list of 100 of them. Some of them are common, some are only used in particular projects...
... -
09:52 Patch #23388: German translation change
- Alright.
I updated the patch and removed the proposed change for @label_day_plural@
I also changed another string on the fly: -
08:57
Patch #23388: German translation change
- Tobias Fischer wrote:
> Looks good to me!
> ...
Understood, this label change is not necessary. We had some users at our company complain about this minor issue so I suggested this change. We did not come across the use as in "since x ... -
09:41 Defect #23377: Don't show "status" field when creating a new version
- _Marius BALTEANU wrote:_
> In my opinion it makes no sense in all pages from where you can add new versions, not only in the modal dialogue. I think there are very few cases when you want to add a locked/closed version.
Yeah, total... -
08:20 Defect #23377: Don't show "status" field when creating a new version
- Marius BALTEANU wrote:
> In my opinion it makes no sense in all pages from where you can add new versions, not only in the modal dialogue. I think there are very few cases when you want to add a locked/closed version.
I agree with yo... -
02:03 Defect #23377: Don't show "status" field when creating a new version
- Tobias Fischer wrote:
> When creating a new version from within the issue form field with the modal dialogue, the "status" option should be hidden.
> ...
In my opinion it makes no sense in all pages from where you can add new versions,... -
01:55 Defect #23377: Don't show "status" field when creating a new version
- I made a patch that fixes/implements this without CSS.
The patch passes all the tests and adds two new assertions:
# new version form doesn't contains the status field
# edit version form contains the status field. -
02:30 Patch #23419 (Closed): Change Japanese translation for label_display_used_statuses_only
- I suggest changing the translation for label_display_used_statuses_only as the following. the sentence will be more concise by this change.
2016-07-24
-
23:21 Feature #23215: Add the possibility to filter issues after Target Version's Status and Due Date
- I've updated the patch to apply clearly on the current trunk (r15732). Is there anything else I can do in order to have this in 3.4.0? (together with the other changes made on queries).
-
16:57 Defect #23412 (Closed): Cannot read git repository with .git in name
- Thank you for your feedback.
-
10:08 Defect #23412: Cannot read git repository with .git in name
- Very sorry was a mistake from myself.
I created my initial git repo for redmine from an empty bare repo.
I have issued a git fetch but on another repo which has a very close name.
Now the results are fine when fetched correctly.
... -
05:00 Defect #23412 (Needs feedback): Cannot read git repository with .git in name
- I cannot reproduce on my CentOS6 Redmine version:3.3.0.
-
16:55 Defect #23414 (Needs feedback): Datepickers don't show in Firefox
- I cannot reproduce on vanilla Redmine version:3.3.0.
-
07:29 Defect #23414 (Closed): Datepickers don't show in Firefox
- Hi.
Redmine version 3.3.0.stable
Ruby version 2.2.2-p95 (2015-04-13) [x86_64-linux]
Rails version 4.2.6
Firefox version 47.0.1.
All datepickers (in Issues especially) don't show (see screenshot in attachments). In Chrome, ... -
09:32 Feature #10999: Ticket list filter: More flexible filter conditions
- Update on July 24
@Jean Louis: Thank you again for your suggestion. I have implemented the two operators on the text field allowing to do boolean search within a text field, so you can search something like:
(word1 OR word 2) AND wo... -
01:16 Patch #23388: German translation change
- Looks good to me!
However, please don't change the label "@label_day_plural@"!
_Tage_ is perfectly well! Example:
* Duration: 2 days – Dauer: 2 Tage
The proposed change _Tagen_ is used in other context:
* In/Since 2 days – In/... -
00:00 Patch #1667: Default tracker setting in each project
- _Jean-Philippe Lang wrote:_
> […] wouldn't it make more sense to set the default tracker on each project member?
What would be the use case for default tracker per project member? I don't see such a business case.
If I remember it c...
2016-07-23
-
17:58 Feature #15520: Markdown formatting
- I updated [[RedmineTextFormattingMarkdown]].
I added the following sentence at the top of the page;
> Currently HTML tags are not allowed by default. See #15520 and #20497 for details.
I tried to make the Markdown wiki page compat... -
17:46 Feature #23413: synchronize Textile and Markdown documents
- I updated [[RedmineTextFormattingTextile]] and [[RedmineTextFormattingMarkdown]]. (#16373-27)
Please double check if I did not break anything.
The attached are help HTML files generated from the wiki pages above. Use them as help ... -
17:38 Feature #23413 (New): synchronize Textile and Markdown documents
- The following contexts are maintained independently even though they share same contents.
* Textile
** wiki page: [[RedmineTextFormattingTextile]]
** help HTML: source:trunk/public/help/en/wiki_syntax_detailed_textile.html
* Markdo... -
17:40 Feature #16373: TextFormatting help for Markdown formatting
- > This issue is closed. Please create a new issue for a new topic.
I've opened #23413.
-
12:31 Feature #16373: TextFormatting help for Markdown formatting
- This issue is closed. Please create a new issue for a new topic.
-
12:12 Feature #16373: TextFormatting help for Markdown formatting
- I've updated [[RedmineTextFormattingTextile]] and [[RedmineTextFormattingMarkdown]].
h3. [[RedmineTextFormattingTextile]]
* Rename the section "Predefined" to "Preformatted Text"
* Add preformatted texts to the section "Paragraph... -
06:14 Feature #16373: TextFormatting help for Markdown formatting
- > So I'd like to propose the following change to sync each other. Do you see any concern or problem?
> ...
I've made these changes.
-
12:16 Defect #23412: Cannot read git repository with .git in name
- Environment :
Environment:
Redmine version 3.3.0.stable
Ruby version 2.2.5-p319 (2016-04-26) [x86_64-linux]
Rails version 4.2.6
Environment production
D... -
12:15 Defect #23412 (Closed): Cannot read git repository with .git in name
- As described in the wiki for repo configuration [[RedmineRepositories]], I created a bare repository by git clone --bare.
I named it myrepo.git and setup the full path name on redmine repository setup as /var/redmine/git_repositories/... -
09:51 Feature #10138: Video Player
- + 1 to me. Now we have to download every attached video file
-
09:50 Defect #23410 (Closed): Error if create new issue and there is no project
- The error occurs in this case
1. install new redmine and there is no project.
2. From top menu, click Project
3. From this project index page, click View All Issue
4. From that issue index page, click on New Issue
Then the error 50... -
04:36 Feature #10999: Ticket list filter: More flexible filter conditions
- Dear Jean Louis
Thank you for your note. I see your point. For the list type fields, this is built-in as far as I understand. For text field in general, I will try to see if I can implement something like your suggestion.
Quan
Je...