Activity
From 2020-06-17 to 2020-06-19
2020-06-19
-
19:03 Defect #33634: The contextual navigation is not working erroneous
- I can confirm the disappearing of the issue navigation controls. The problem is reproduced by following the described steps.
The Redmine instance is running in Docker (official image): -
12:16 Defect #33634 (New): The contextual navigation is not working erroneous
- *My system*
* Database manager version: MySQL 5.7.29
* Ruby version: 2.6.6-p146 (2020-03-31) [x86_64-linux]
* Rails version: 5.2.4.2
* Redmine version: 4.1.1.stable
*The issue*
The "« Previous" and "Next »" links found on any...
2020-06-18
-
21:51 Feature #33631 (New): Custom fields totals fro parent-child issues
- When we have a parent-child issue relation, some of the standard fields are calculated based on child issues. For fields like estimated time and spend time we have totals (sum) calculated and presented on the issue page. There is also is...
-
17:07 Defect #33629 (New): 403 on Versions via API and individual versions via WebUI and API
- When trying to get a listing of the project's version or information on an individual version via the API, Redmine replies with a 403 error. A similar happens when clicking a version, like in the file overview of a project, I get a 403 e...
-
11:39 Defect #33626: Keep issue status when processing commit messages
- Thank you Mischa for the quick reply
The issue to me is that when leaving the *Applies Status* blank the revisions fail to be linked to the issues.
I would expect either:
* when leaving the *Applied Status* blank that revisions ge... -
11:23 Defect #33626: Keep issue status when processing commit messages
- Changed description to use Redmine message link instead of external direct link.
FWIW: I don't get the problem of the OP of that forum thread. What he describes with:
> We are using the keyword "for" to mark commits that refer to a... -
10:25 Defect #33626 (New): Keep issue status when processing commit messages
- Described well in [message#57210]
Confirmed using:
Ruby 2.3.8
MySQL 5.7
Redmine 4.1.1
Rails 5.2.4.2 -
08:16 Patch #33624 (Closed): Traditional Chinese translation (to r19829)
- Committed the patch. Thank you for your contribution.
-
06:05 Patch #33624 (Closed): Traditional Chinese translation (to r19829)
- * New tags added
** setting_email_domains_allowed, setting_email_domains_denied, field_passwd_changed_on, label_relations_mapping, label_import_users, label_days_to_html
-
08:15 Revision 19830 (svn): Traditional Chinese translation update (#33624).
- Patch by ChunChang Lo.
-
04:52 Feature #1422 (Closed): Date selection for Activity Page
- Committed the patch attached in #1422#note-22 with slight modifications. Thank you for your contribution.
-
04:52 Revision 19829 (svn): Update locales (#1422).
-
04:49 Revision 19828 (svn): Date selection for Activity page (#1422).
- Patch by Mizuki ISHIKAWA.
-
01:41 Defect #31287: Ordering wiki pages should not be case sensitive
- Not only PostgreSQL but SQLite is also affected.
!{width: 176px; border: 1px solid grey;}.sqlite.png!
2020-06-17
-
17:32 Feature #22802: Add the posibility to set/change the position of an issue in a version
- Fix default order
-
13:41 Feature #22802: Add the posibility to set/change the position of an issue in a version
- Hello,
Just add the possibility to sort issues by position from the REST API.
Example: -
12:06 Feature #22802: Add the posibility to set/change the position of an issue in a version
- Ordering by priority/start date can be useful but as said, it's not as easy as drag/dropping issues to reorder them.
For me ordering is not always a matter of showing the chronology (or any other existing criteria) of the TODO list.
Th... -
16:38 Defect #33616 (Closed): Assignee & Author Dropdown Sort
- In Redmine 4.1.1.stable, the Assignee and Author dropdowns seems to be in a random order.
Redmine plugins:
redmine_agile 1.5.3
redmine_issue_dynamic_edit 0.7.2
In the "Issues" tab, we add "Assignee", and see:... -
11:45 Feature #16523 (Closed): RESTful API: Expose custom fields project relations
- Tom Quern wrote:
> Or is this is duplicate (and fixed by) #33301 ?
You are right. The feature will be available in the upcoming Redmine 4.2.0. -
10:53 Feature #16523: RESTful API: Expose custom fields project relations
- Or is this is duplicate (and fixed by) #33301 ?
-
10:46 Feature #16523: RESTful API: Expose custom fields project relations
- This feature request is 6 years old. Are there any plans to eventually implement it?
An alternative approach to what was suggested above could be adding another parameter to the projects endpoint i.e. /projects.xml?include=custom_fiel... -
11:06 Feature #33612: Expose repository version via REST API
- On a similar note, being able to get the current value for the 'Maximum attachment size' setting would be also great. I you think this should be a separate request I'm happy to create another ticket to track it.
-
11:00 Feature #33612 (Closed): Expose repository version via REST API
- For Redmine clients interacting with different versions of the Redmine server it would be beneficial to have an easy way to identify the server version. Currently this information is available in the web UI: <your-host>/admin/info and ca...
-
10:54 Defect #33402: Receive email problem - inserting unwanted p tags
- Hello @Andrej
did you manage to figure out what was wrong.
I've got exactly the same issue.
Environment:
Redmine version 4.1.1.stable
Ruby version 2.5.5-p157 (2019-03-15) [x86_64-linux-gnu]
... -
08:05 Defect #33610 (Closed): Submitting the issue edit form without changes unexpectedly updates updated_on
- The procedure below updates @updated_on@ column in @issues@ table, even though any fields on the issue are not updated and no journal is created.
*Steps to reproduce:*
1. Open the edit issue form
2. Click the Submit button without...