Redmine

h1. Bugday's Integration List

This is a list of issues brought up by several users/contributors in the light of a Bugday's integration (see message#35571). This list is divided by users/contributors who mentioned the issues.

All issues mentioned in the forum-thread upto 2013-03-17 20:23 are transported into this list.

h2. Daniel Felix

* #12730 -- Maybe you can check the patches on #12730 and its relations. Do they still clean apply to the current trunk? Maybe they could get included.

h2. Dipan Mehta

* #11056 actually works but but is a peculiar behavior. If this is as per the expected behavior, the issue can be closed.

* #429 & #1233 -> can be strait away solved by "start_page plugin":http://www.redmine.org/plugins/redmine_startpage 

* #1306 - works out of the box.

* #1158 - can be done partially with plug-in

* #1255 - please set the issue to Need feedback

* #1707 - can be done through plugin

* #1966 - works out of the box.

* #2748 - Invalid (may be issues can be created using commandine or via REST API) 

* #2558 - works out of the box.

* #2565 - Not very sure, but current functionality is sufficiently doable.

* #2637 - works out of the box. (just need watchers)

* #2709 - duplicates #482 (also plugin available  "redmine_default_assign":https://github.com/giddie/redmine_default_assign ) 

* #2792 - works out of the box.

* #2725 - very ambiguous! 

* #2768 - not exactly out of the box but very close. [email created issues _can_ have project_id set for themselves]

* #1894 - can be done through plugins

* #1991 - dup of #1710

* #2809 - works out of the box. 

h2. Ivan Cenov

* #811: Username validation - allow spaces... -- There is a patch given in the issue. If this patch is safe it could be implemented.

* #867: Want more wiki link types -- I have impression that this is already implemented, so #867 could be closed.

* #709: Show attached images on issue body -- Attached images may be shown in issue body. This issue could be closed...

* #1069: "Help" link should launch new page. -- IMHO, this should not be implemented, because while some people want this, other people do not want it. So, let default behavior remain as is.

* #1030: Adding comments is not an "activity"? -- Adding comments (notes) to issues is is reported in Activity; 1030 could be closed.

* #1022: Patch for #1003: Allow "New Issue" from anywhere -- This is outdated, I tried with current trunk and it did not work. May be #1022 and #1003 should be closed?

* #1265: Add ability to delete Versions -- Deleting versions is implemented. Redmine asks "Are you sure?" and then tries deleting. However deleting does not proceed if versions have issues assigned. I think this issue could be closed.

* #1192: IE 6.0 Timeout Problem -- Who uses IE 6.0 nowadays? This issue could be closed.

* #1231: project-name to short -- Nowadays, projects can have names at least 80 characters long. I think this issue could be closed.

* #1221: user should have permissions which can edit/delete the messages posted by himself -- This is already implemented and #1221 can be closed. Implemented permissions are: 

•Manage forums

•Post messages

•Edit messages

•Edit own messages

•Delete messages

•Delete own messages

* #1294: Gantt Chart: Show/Hide Right Menu -- The plugin https://github.com/ries-tech/sidebar_hide does this job. I think this issue could be closed.

* #2048: Code Review Module -- There is a plugin http://www.redmine.org/plugins/codereview. In my opinion it is very good and I propose #2048 to be closed.

* #2184: Command line ticket creation? -- On Redmine's side REST API for creating issues is available. In my opinion #2184 could be closed....?

* #5306: Separation of core and Redmine plugins -- This issue is outdated. Should be closed.

* #5303: Add spent_hours to /issues/index API -- I feel that the author of the issue needs http://www.redmine.org/projects/redmine/wiki/Rest_TimeEntries and it is already implemented. If this is true, it could be closed.

* #5381: Issues of a deleted project are not deleted -- Tested just now: deleting project deletes its issues. Also tested with two projects with related issues:

P1x with issue i1

P1y with issue i2; i2 follows i1.

Deleted P1y, i2 was deleted too, the relation in i1 was deleted (right).

So, I feel that #5381 is a candidate for closing.

* #5342: Add tracker information to projects in REST API -- I think this is already implemented: http://www.redmine.org/projects/redmine/wiki/Rest_Projects. http://www.redmine.org/issues/5342#note-2. Another candidate for closure...

* #5470: Avoid duplicate issue creation -- I commented in the issue: http://www.redmine.org/issues/5470#note-2. To close or not ... I don't know ...

* #5551: Unable to edit issue - Description field is blank and not written to database on submit -- It seems this problem is specific to the author's Redmine instance. It has never happened in my practice. The issue is too old, related to ancient Redmine and in my opinion is a candidate for closure.

* #3494: Browser "Back" to issue list displays wrong filter -- Similar to #5551, old Redmine, old Firefox. I commented in the issue http://www.redmine.org/issues/3494#note-14. A candidate for closure.

* #3398: List assigned issues to the specified user -- I commented in the issue http://www.redmine.org/issues/3398#note-5 (this is solved by a plugin). My opinion is to close this issue.

h2. Max Horn

* #730: Patch for #728 (display update timestamp outside yellow ticket) -- issue #728 was rejected, so this could be closed

* #1022: Patch for #1003 -- issue #1003 was just rejected by Daniel ;-)

* #3496: "Assign To" filter on "View all issues" page allows to select user which cannot be assigned

* #8935: Password reset is required before a user can login after upgrading from 0.9.1 to 1.2.1 -- This is (a) outdated, and (b) it was not reproducible and the author also suggested that he made a mistake.

* #10598: wrong email setting in configuration.yml preventing redmine server from starting