Activity
From 2018-01-23 to 2018-01-25
2018-01-25
-
18:14 Defect #28078 (Closed): Workflows inconsistencies when removing "add/edit issue" permission to a role which already has a workflow defined
- I've tested this on a vanilla Redmine (3.4):
Steps to reproduce, as admin:
Setup:
- Set 2 new roles with add/edit issues permission. We have: Role A, Role B
- Set 1 new Tracker: Tracker A
- Set 3 new statuses: Status A, Stat... -
17:50 Feature #28077 (New): Hide issue-list header of any query-result by configuration or theme
- Hide issue-list header of any query-resukt
by configuration or an userdepended theme.
Background:
After execute a query at least there are shown checkboxes and the issue-number as a header-column of the list inspite of selecting no co... -
15:53 Feature #18556: Raise the limit of attachments at once from 10 to 50 and make it configurable in configuration.yml
- Here is my rough first attempt at changing this. I'm running redmine 3.3.1 so the patch would need some updated to apply to latest.
-
15:34 Feature #15902: Custom Field - Version - Combo list to be grouped by projects..
- FTR.
According to #9850#note-19, r16194 (#23265) prefix project name at version-format custom field in issue list. -
15:19 Feature #9850: Differentiate shared versions in version-format custom field drop-downs by prepending its project name
- Edgars Batna wrote:
> P.S.
> ...
Indeed.
I think it is covered in #9851 and #15902. -
14:33 Feature #28070 (Closed): How to upgrade Redmine 3.3.4 to 3.3.6
- Please use forum for question after reading "How to request help":http://www.redmine.org/boards/2/topics/667.
And I recommend you to read [[RedmineUpgrade]]. -
11:01 Feature #28070 (Closed): How to upgrade Redmine 3.3.4 to 3.3.6
- Dear Team,
Can you please help what is the steps and backups need to follow for upgrade Redmine 3.3.4 to 3.3.6
-
11:25 Defect #27863: If version is closed or locked subtasks don't get copied
- Hi,
for me all children issues must be copied independently from the state of the version, not only the parent task.s
Regards
Alessandro
-
10:44 Defect #28069 (New): Queries 403 error if query author is not in the roles list
- How to reproduce (with vanilla redmine 3.4):
- Go to a project where you are a member with Role A
- create a query and save it. make it visible to Role B
- Save the query
Result:
- Error 403
In my opinion, a query should al... -
10:41 Defect #27884: RTL wiki class broken in Redmine 3.2.6
- I've just noticed that HTML emails sent from Redmine will contain class="wiki-class-rtl" for RTL text, which is not supposed to work because email clients have no access to Redmine css.
-
07:14 Feature #28067 (Closed): Add context menu for issues in calendar
- #10485 has added a context menu for issues on gantt page. I think it improves usability and consistency if calendar page has the same context menu for issues.
2018-01-24
-
20:48 Defect #22424: Change Russian translation for default_issue_status_feedback
- *Требуется ответ* or *Ожидается ответ* is same meaning as *Нужен отклик*.
I thought could me to suggest *запрос* (request) в качестве статуса. Suggestion *ответ* (requests) is helpfull to understand that it makes sence. All issue stat... -
19:16 Defect #22424: Change Russian translation for default_issue_status_feedback
- The translation *Требуется обратная связь* will have the same meaning as *Нужен отклик* in this context, but is shorter. The latter is important, as noted by Serguei Okladnikov.
Actually, *Требуется ответ* (response/answer needed) or ... -
20:05 Feature #27877: Optimize history navigation
- In gantt and calendars you have links to go forward or back in time.
1. Don't show back or forward button/links if there is no info for the future or past.
2. Skip blank time areas on clicking on forward or back. If there are 6 month... -
19:19 Feature #27877 (Needs feedback): Optimize history navigation
- Please explain more details.
-
18:57 Defect #28035 (Needs feedback): Order of versions is not correctly ordered
-
18:57 Defect #28035 (New): Order of versions is not correctly ordered
-
18:57 Defect #28035 (Closed): Order of versions is not correctly ordered
- source:tags/3.4.4/app/models/version.rb#L197
-
18:08 Defect #27863 (Confirmed): If version is closed or locked subtasks don't get copied
- Confirmed.
In the log: -
14:02 Defect #28062: "Error 500" when creating a new task for a specific sprint
- Thank you for your guidance, Mr. MAEDA and Mr. BALTEANU. I already opened a ticket for the plugin author.
Go MAEDA wrote:
> I glanced through the log and found the fllowing lines:
> ...
-
03:49 Defect #28062: "Error 500" when creating a new task for a specific sprint
- I glanced through the log and found the fllowing lines:
-
13:12 Patch #28026 (Closed): "project_from_subbaddress" option is not listed in the help of "rake redmine:email:receive_imap"
- Committed.
-
09:50 Defect #22977: A project member has no access and gets no notification, when being a watcher of the issue
- Well, I see the difference between SEE and BE NOTIFIED, no doubt. What is the expected behaviour? To see (might be expected, when the verb WATCH was used), or get notified?
-
09:42 Defect #22977: A project member has no access and gets no notification, when being a watcher of the issue
- I still think SEEING the issue and being NOTIFIED on issue updates are two completely separate things. Being able to add the issue creator (via e-mail) as a watcher for him/her to receive notifications that something has changed/happened...
-
09:49 Feature #8488: Create an 'Involve' mechanism to private issues
- +1
-
09:48 Defect #11888: No e-mail notification for non-members who are watchers
- +1
-
09:44 Defect #24061: Tickets can be watched by users who are not available in specific tracker
- Wouldn't a better solution be to
* Configure if issues should be "watchable" by users not in the selected tracker
* If a user not in the selected tracker is allowed to be added to watchers, RM should honor that and notify that user
-
04:55 Patch #28024 (Closed): Fix typo in error message in mailer.rb
- Committed. Thank you for your contribution.
2018-01-23
-
20:00 Defect #28062: "Error 500" when creating a new task for a specific sprint
- Marius BALTEANU wrote:
> Please contact plugin author.
> ...
Mr. Marius BALTEANU, I opened the ticket according to the instructions of the author of the plugin. You or some moderator can help me on this issue, which I have noticed, re... -
19:34 Defect #28062 (Closed): "Error 500" when creating a new task for a specific sprint
- Please contact plugin author.
This is the Redmine issue tracker for reporting bugs or feature requests about the Redmine core software.
-
19:30 Defect #28062 (Closed): "Error 500" when creating a new task for a specific sprint
- I am dropping into an *Internalerror 500* page when creating a new task, of type functionality for specific sprints. Apparently it is something related to the *Scrum plugin*, which is even in its latest stable version (0.18).
-
13:30 Feature #5358: Share Issues Categories for sub-projects
- +1
-
12:07 Feature #1330: Copy a Wiki Page
- +1 would be very useful
-
02:50 Defect #28033: Unable to turn off "For all projects" flag of custom queries
- It is because queries with "For all projects" enabled don't have the information of its belonging project.
The attribute @IssueQuery.project@ indicates the query's belonging project, but the value is nil for queries "for all projects"...